Data migration route
Doc.It Suite data to SQLite
Doc.It Suite is a document management system for accounting firms, and SQLite is a store of data kept as files the firm holds. What lands in SQLite is the register: every file’s name, place, dates and details, with the files themselves stored beside it.
Doc.It SuiteDocument management- Matters: Exported in full
- Tasks: Exported in full
- Documents: Exported with mapping
- Contacts: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
SQLiteFiles- 2 carried
- 1 mapped
- 6 to confirm
What moves
What moves from Doc.It Suite to SQLite
Each row is a kind of record Doc.It Suite holds, whether SQLite has a place for it, and what is planned. On this route two kinds of record carry across, one kind needs mapping and six kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partEngagements are organised as client Work Binders, not as legal matters. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | To be confirmed | Has a placeContacts and their roles on matters as linked tables. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | HeldHeld in the Inbox, in Work Binders and in the Archive, named by the firm’s policy. | Has a place in partListed in a table; the files themselves stay in folders beside the database. | Exported with mapping |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partAs message files in folders, indexed in a table. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeA notes table linked to matters. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeA table of dated entries, with no calendar view. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partWork Binders carry status, due dates and routing between staff. | Has a placeA table of tasks and their status at the final date. | Exported in full |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeColumns added to the table they belonged to. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | No placePrecedent files are kept in folders, not in the database. | Confirmed in the analysis |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against Doc.It Suite.
- Exported with mapping
- SQLite holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.
This kind of move
The files, and a register of what each one is.
A database is a poor place to keep documents and a good place to keep facts about them. On this route the files from Doc.It Suite are exported to storage the firm controls, and SQLite receives the register: one row per file, with its path, size, dates, author and whatever profile or folder details existed. That register is what makes a large export searchable. It also proves completeness, since the row count and total size can be agreed to the source.
How useful the register is depends on how much Doc.It Suite knows about each file. A document management system has a profile to carry. A plain folder has only a path and dates, and the client or matter has to be read out of folder names. Where versions or an audit history exist, each becomes a table of its own. The export is checked by picking documents at random in the source, finding them through SQLite, and opening the file to confirm it is the same one.
How Doc.It Suite is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Doc.It Suite stays untouched until the copy in SQLite has been checked.
Where the data is now
Leaving Doc.It Suite
Doc.It was designed around the way an accounting engagement runs, so its content is in one of three states: waiting in the Inbox, live in a Work Binder, or filed in the Archive. A move has to collect all three. For binders it also has to settle whether work in progress is finished first or carried across part-way through, with its status.
Inbox, binders and archive
Documents in the Inbox have not been filed yet and may belong to nobody. Work Binders hold current engagements with status and routing. The Archive holds the settled record. Each is exported and counted on its own. The Inbox is best emptied by the firm before the freeze, because unrouted scans have no client attached.
Policy Manager names the files
File names and storage locations follow a firm-wide policy applied as documents are gathered. That helps: the client, year and document type can often be read back out of the name and path. The policy is obtained first and tested against real files, since it may have been revised more than once.
Engagements are not matters
Accounting work recurs by client and year: a tax return for one year, an audit for the next. A legal system expects matters. The mapping decides whether each client becomes one continuing matter with year folders, or one matter per engagement. That choice changes the matter count considerably and is agreed before the trial load.
Files from other programs
The Inbox can pass documents on to other binder systems such as CaseWare, and Doc.It works beside tax and practice software. Files produced by those programs open only in them. They are carried across as they are, and the firm confirms it will keep the software needed to read them.
Where it is installed
The suite has been offered on-premise, hosted and as a hybrid of the two, so the documents may be on the firm’s own server or with a provider. Finding out which, and who can give read access, is the first practical step, ahead of any discussion about mapping.
Where it is going
Arriving in SQLite
A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.
One file, kept with the archive
Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.
No logins inside the file
SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.
Built for reading, not sharing
Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.
Documents stay outside it
Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.
Someone has to open it
SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Doc.It Suite holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Doc.It Suite holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to SQLite as a trial and checked against Doc.It Suite: record counts, totals where Doc.It Suite holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Doc.It Suite, the export is run a final time and checked again. There is nothing to go live. Doc.It Suite is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in Doc.It Suite and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.
Step 1 of 5
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Doc.It Suite holds
What is in it, how its records link, and where each piece would sit in SQLite. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- A fixed price in writing
Set after the analysis, so it reflects what is in your data. You have it before any work starts.
Beyond the data
Structure, permissions and handover
SQLite is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.
What is agreed and set up
- File name, storage location and whether a second copy exists
- Whether a checksum is recorded for later verification
- Saved queries for matter, ledger and document look-ups
- Which tool staff will use to open the file
- Who may open the folder the file sits in
- Retention period and destruction date noted beside the file
Questions
Doc.It Suite to SQLite: what firms ask
Is Doc.It Suite still a current product now that IRIS owns it?
IRIS acquired Doc.It in 2021 and its website still refers to existing IRIS Doc.It customers. It also sells a newer cloud product, IRIS Document Management, which it says is available to those customers. Whether to stay, take that, or go elsewhere is the firm’s decision. The extraction approach does not change.
Can archived client files go into a legal document system?
Yes, as documents filed under a client and a matter. The Archive’s structure, whatever the firm’s policy made it, is mapped to the destination’s folders or profile fields. What will not carry over is workflow status. Open work is either completed before cutover or listed for the firm to set up again as tasks.
Does the copy in SQLite hold documents from Doc.It Suite?
In part. Listed in a table; the files themselves stay in folders beside the database. What SQLite can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without Doc.It Suite.
Does everything in Doc.It Suite have a place in SQLite?
Most of it does on paper. Contacts, emails, notes, calendar entries, custom fields and templates could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in SQLite is kept as a readable archive, and you see which before the move.
What has to be decided before Doc.It Suite is written out to SQLite?
Documents are exported with mapping, so each mapping is agreed with you first. Contacts, emails, notes, calendar entries, custom fields and templates are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Doc.It Suite and into SQLite
Where to start
Before and after the move.
Choosing the system comes before a migration. Setting it up and putting AI to work come after.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Doc.It Suite and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from Doc.It Suite to SQLite?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.