Data migration route
INSZoom to Server drives migration
INSZoom is a cloud case management system for immigration work, and Server drives are plain files on equipment the firm controls. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
INSZoomCloud- Documents: Carried across
- Emails: Carried with mapping
- Templates: Carried 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
Server drivesFiles- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Billing: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 2 mapped
- 5 to confirm
- 5 archived
What moves
What moves from INSZoom to Server drives
Each row is a kind of record INSZoom holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, five kinds have no place in Server drives and are 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. | No placeA matter becomes a folder; its details survive only in an index file. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldPrivate individuals and corporate clients; HR contacts can have portal access (Enterprise). | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldDigital case files, with documents collected from clients. | Has a placeFiles in folders, named and dated during the load. | Carried across |
| 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 .msg or .eml files in each matter’s correspondence folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs a text or PDF file per matter, not as separate records. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partDeadline and expiry notifications; a general appointment calendar was not confirmed. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | No place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | No placeOnly as exported reports or spreadsheets. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | HeldInvoice generation, with integrations to QuickBooks Online, LawPay and Authorize.net. | Has a place in partInvoices as PDF files; no ledger. | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No placeOnly as exported ledger reports kept as files. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | No place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldForms library, digital questionnaires and email templates. | Has a place in partPrecedents as Word files; merge fields tied to the old system stop working. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partAdvance Case Request lets corporate clients start a case (Enterprise edition). | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Server drives has a place for this kind of record. It is loaded there and checked against INSZoom.
- Carried with mapping
- Server drives 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
- Server drives 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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from INSZoom into Server drives means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Server drives do not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in INSZoom.
INSZoom is hosted by its maker and Server drives sit 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 Server drives
Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.
Agree the tree and the names
A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.
Budget the path length
Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.
Dates have to be set deliberately
A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.
Emails become message files
Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.
Keep an index beside the files
A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what INSZoom holds and how it is organised, then agree with you where each kind of record will sit in Server drives. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into Server drives and checked against INSZoom: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
There is no financial cutover on this route. After a short freeze on changes in INSZoom, a final pass over a weekend picks up what changed since the trial. INSZoom is kept read only as the fall-back record.
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 Server drives. 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
Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.
What is agreed and set up
- Share and top-level folders for clients, precedents and administration
- Security groups and folder permissions, with restricted matters separate
- Drive letter mapped for every user at sign-in
- Backup schedule and shadow copies for earlier versions
- Written naming rule for client, matter and document names
- Read-only area for closed matters and archived system exports
Questions
INSZoom to Server drives: 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.
Do trust balances in INSZoom have a place in Server drives?
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. If Server drives turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
What happens to records Server drives have no place for?
On this route that is matters, contacts, calendar entries, billing records and intake records. 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 data is loaded into Server drives?
Emails and templates are carried 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 which closed matters and how many versions of a document are in scope.
Other routes
Other routes from INSZoom and into Server drives
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 Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from INSZoom to Server drives?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.