Data migration route
INSZoom data to SQLite
INSZoom is a cloud case management system for immigration work, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what INSZoom holds and keeps it readable and open to queries.
INSZoomCloud- Matters: Exported in full
- Contacts: Exported in full
- Calendar: Exported in full
- Billing: Exported in full
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SQLiteFiles- Templates: Kept as a readable archive
- 5 carried
- 2 mapped
- 5 to confirm
- 1 archived
What moves
What moves from INSZoom to SQLite
Each row is a kind of record INSZoom holds, whether SQLite has a place for it, and what is planned. On this route five kinds of record carry across, two kinds need mapping, one kind has no place in SQLite and is archived and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldImmigration cases with phases and milestones, for US, Canadian and other countries’ processes. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldPrivate individuals and corporate clients; HR contacts can have portal access (Enterprise). | Has a placeContacts and their roles on matters as linked tables. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldDigital case files, with documents collected from clients. | 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 | Held in partTemplated emails and reminders are sent from the system in the Enterprise edition. | Has a place in partAs message files in folders, indexed in a table. | Exported with mapping |
| 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 | Held in partDeadline and expiry notifications; a general appointment calendar was not confirmed. | Has a placeA table of dated entries, with no calendar view. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeA table of tasks and their status at the final date. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a placeA table of time and expense entries. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | HeldInvoice generation, with integrations to QuickBooks Online, LawPay and Authorize.net. | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeTrust transactions as rows, for look-up and not for accounting. | Confirmed in the analysis |
| 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 | HeldForms library, digital questionnaires and email templates. | No placePrecedent files are kept in folders, not in the database. | Kept as a readable archive |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partAdvance Case Request lets corporate clients start a case (Enterprise edition). | Has a placeAn enquiries table, where the source tracked them. | Exported in full |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against INSZoom.
- 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.
- Kept as a readable archive
- SQLite has no place for it. It is exported in a format that opens without INSZoom and handed to the firm as a read-only archive.
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
Not a new system. A complete copy the firm can query.
Writing INSZoom out to SQLite is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in INSZoom as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
INSZoom is hosted by its maker and SQLite sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What INSZoom will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving INSZoom
INSZoom is built for volume immigration work, much of it for employers. A move off it has to keep three things joined up: the company that sponsors, the employee the case is about, and the history of each case’s phases. Documents and invoices are the simple part. The forms data and the reporting that corporate clients receive take the planning.
Employers, HR contacts and employees
A corporate client has HR contacts who log in, and many employees who each have their own cases. That is three levels where most practice systems have a client and a matter. The analysis decides whether the employer becomes the client with one matter per employee case, and where the employee’s own details are then kept.
Cases outside the United States
The system handles Canadian and other countries’ immigration processes as well as US ones, each with different forms and steps. A destination set up around USCIS case types will not have a place for a Canadian work permit. Every case type in use is listed by country before mapping starts, with a count against each.
Phase and milestone dates
Cases are tracked through phases and milestones so that turnaround can be reported to corporate clients against a service level. Those dates are history a client may ask about later. They need date fields of their own in the new system, or a dated summary on each matter if it has none.
Questionnaire answers behind forms
Clients complete digital questionnaires and the answers fill the forms library. Receipt details from USCIS notices are also read into the case. Completed forms are carried as documents. The answers themselves are mapped field by field, and the ones with no destination are listed for the firm instead of being dropped quietly.
Invoices here, ledger elsewhere
Invoices are raised in INSZoom and can be passed to QuickBooks Online, with payments through LawPay or Authorize.net. So the invoice history is in one place and the firm’s books in another. Debtor balances are taken from both and compared before cutover, and any difference is explained while the old system can still be queried.
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 INSZoom holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything INSZoom 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 INSZoom: record counts, totals where INSZoom 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 INSZoom, the export is run a final time and checked again. There is nothing to go live. INSZoom 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 INSZoom 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 INSZoom 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
INSZoom to SQLite: what firms ask
Our corporate clients use the HR portal. What do they lose?
Their logins end with the old system. What they saw there, such as case status, documents and reports on their employees, has to be offered another way. If the destination has a client portal, HR contacts are invited to it after cutover. If not, the firm agrees a reporting routine with each client before go-live.
Can cases in progress be moved without losing their place?
Yes, provided the current phase and its dates are mapped. Each open case is loaded with its status, the milestones already reached and the deadlines still ahead. In the trial load a sample of open cases is opened side by side with INSZoom to confirm the next step and its due date agree.
Does our forms library move?
No. The library belongs to the product and is kept current by Mitratech. What belongs to the firm is each client’s data and each completed form. If the destination is another immigration system it has its own library. If it is a general practice system, form preparation needs a separate tool.
Does the copy in SQLite hold trust ledgers from INSZoom?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in INSZoom before the plan is fixed.
What happens to records SQLite has no place for?
On this route that is templates. They are exported from INSZoom in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before INSZoom is written out to SQLite?
Documents and emails are exported with mapping, so each mapping is agreed with you first. Notes, tasks, time entries, trust ledgers and custom fields 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 INSZoom 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.
INSZoom and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from INSZoom 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.