Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

INSZoom to Lawmatics migration

INSZoom is a cloud case management system for immigration work, and Lawmatics is a cloud CRM and intake system. This route carries people and their history into Lawmatics, and the table shows how much of the firm’s files and money has a place there.

FromINSZoomCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Calendar: Carried across
  4. Intake: Carried across
  5. Documents: Carried with mapping
  6. Emails: Carried with mapping
  7. Billing: Carried with mapping
  8. Templates: Carried with mapping
  9. Notes: Confirmed in the analysis
  10. Tasks: Confirmed in the analysis
  11. Time and expenses: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
ToLawmaticsCloud
  • 4 carried
  • 4 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from INSZoom to Lawmatics

Each row is a kind of record INSZoom holds, whether Lawmatics has a place for it, and what is planned. On this route four kinds of record carry across, four kinds need mapping and five kinds are confirmed in the analysis.

Records in INSZoom and their place in Lawmatics
RecordIn INSZoomIn LawmaticsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration cases with phases and milestones, for US, Canadian and other countries’ processes.Has a placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage.Carried across
ContactsClients, other parties and referrersHeldPrivate individuals and corporate clients; HR contacts can have portal access (Enterprise).Has a placeContacts and companies load from CSV; relationships link further parties to a matter.Carried across
DocumentsFiles stored in or linked from the systemHeldDigital case files, with documents collected from clients.Has a place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import.Carried with mapping
EmailsEmails saved to matters or to the storeHeld in partTemplated emails and reminders are sent from the system in the Enterprise edition.Has a place in partEmails reach a matter through mail sync from a connected mailbox.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeNotes on matters, contacts and companies.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partDeadline and expiry notifications; a general appointment calendar was not confirmed.Has a placeAppointments, called events, with types and locations.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a place in partTime entries and expenses, where the Time & Billing module is enabled.Confirmed in the analysis
BillingInvoices, payments and debtor balancesHeldInvoice generation, with integrations to QuickBooks Online, LawPay and Authorize.net.Has a place in partInvoices and payments; a past invoice is entered as sent, then marked paid.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partA trust account with a running balance; deposits are allocated to a contact and matter.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeMatter, contact and company fields. A field must exist before data is imported into it.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldForms library, digital questionnaires and email templates.Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partAdvance Case Request lets corporate clients start a case (Enterprise edition).Has a placePipelines and stages, marketing sources and campaigns.Carried across

What the plans mean

Carried across
Lawmatics has a place for this kind of record. It is loaded there and checked against INSZoom.
Carried with mapping
Lawmatics 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

People and history move. Files and accounts stay.

A CRM wants to know who the firm knows and what has passed between them. From INSZoom that means contacts, their roles, their matters as a history of work done, and the referrers who sent them. Loaded into Lawmatics, a past client becomes someone the firm can contact again with that history in view. That is usually the reason for this route: the firm is adding an intake and marketing system beside its matter system, or replacing the front end of it.

A CRM is not usually where documents, time, billing and trust are kept, and the table above shows what Lawmatics takes. What it does not take stays in INSZoom or its successor. So the plan has to say which system is the master for a contact once both are running, or the two lists drift apart. Contacts are de-duplicated before the load, and anyone who has asked not to be contacted is flagged in Lawmatics from the first day.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of INSZoom depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to INSZoom is kept running until the checks on Lawmatics are finished.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off INSZoom

Where it is going

Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.

  1. Contacts and matters load separately

    The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.

  2. Set up before loading

    Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.

  3. Statuses and matter numbers

    Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.

  4. Duplicates are matched by email

    With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.

  5. What has no place

    There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.

More about moving into Lawmatics

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what INSZoom holds and how its records link, then agree with you, field by field, where each piece will sit in Lawmatics. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in INSZoom, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Lawmatics as a trial and checked against INSZoom: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in INSZoom are frozen for an agreed window, the data is collected a final time and Lawmatics goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in INSZoom as at the cutover date. 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

Step 1 of 5: Start with the route

Moving fromINSZoom
Moving toLawmatics

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what INSZoom holds

    What is in it, how its records link, and where each piece would sit in Lawmatics. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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

Setting up Lawmatics

Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.

In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.

Set-up decisions in Lawmatics

  • Pipelines and stages for intake and for open matters
  • Practice areas, sub-statuses, relationship types and the matter numbering pattern
  • Custom fields on matters, contacts and companies
  • Intake forms, booking links and e-signature document templates
  • Follow-up automations, with marketing sources and campaigns
  • Mail and calendar sync, user roles and practice system integration

Questions

INSZoom to Lawmatics: 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 Lawmatics?

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 Lawmatics turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in INSZoom have a place in Lawmatics?

Most of it does on paper. Notes, tasks, time entries, trust ledgers and custom fields 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 Lawmatics is kept as a readable archive, and you see which before the move.

What has to be decided before INSZoom data is loaded into Lawmatics?

Documents, emails, billing records 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 sets the cutover date and how much financial history comes across as live records.

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.

How we do itDiscovery to rollout, step by step

INSZoom and Lawmatics are the names and marks of their owners, used here only to identify the two systems.

Moving from INSZoom to Lawmatics?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.