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

Data migration route

INSZoom to Litify migration

INSZoom is a cloud case management system for immigration work. Litify is a case management system, run the same way. The records line up case for case, and the detail is in the fields and stages.

FromINSZoomCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Intake: Carried across
  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
ToLitifyCloud
  • 5 carried
  • 3 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from INSZoom to Litify

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

Records in INSZoom and their place in Litify
RecordIn INSZoomIn LitifyWhat 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 placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldPrivate individuals and corporate clients; HR contacts can have portal access (Enterprise).Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldDigital case files, with documents collected from clients.Has a placeLoaded to the document component and attached to matters.Carried across
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 partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partDeadline and expiry notifications; a general appointment calendar was not confirmed.Has a placeCalendar events on the matter.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 placeTime entries on the matter.Confirmed in the analysis
BillingInvoices, payments and debtor balancesHeldInvoice generation, with integrations to QuickBooks Online, LawPay and Authorize.net.Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedTo be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields are created before loading.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldForms library, digital questionnaires and email templates.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partAdvance Case Request lets corporate clients start a case (Enterprise edition).Has a placeLoaded as intakes.Carried across

What the plans mean

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

Case to case, field by field.

Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. INSZoom and Litify may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.

Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Litify, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.

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 Litify 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

Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in INSZoom and checking each trial against INSZoom.

  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 Litify. 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 Litify 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 Litify 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 toLitify

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

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

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

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 Litify 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 Litify?

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 Litify is kept as a readable archive, and you see which before the move.

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

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 Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from INSZoom to Litify?

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

We reply within one business day.