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

Data migration route

LawLogix Immigration Case Management to Litify migration

LawLogix Immigration Case Management 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.

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

What moves

What moves from LawLogix Immigration Case Management to Litify

Each row is a kind of record LawLogix Immigration Case Management holds, whether Litify has a place for it, and what is planned. On this route five kinds of record carry across, one kind needs mapping and eight kinds are confirmed in the analysis.

Records in LawLogix Immigration Case Management and their place in Litify
RecordIn LawLogix Immigration Case ManagementIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration cases, each following a workflow for its case type.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldForeign nationals and employers, with HR users on their own portal.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldCase files and documents collected through the portals are stored digitally.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partDeadlines are monitored through reporting; a full 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 balancesTo be confirmedHas a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedTo be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo 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 automationHeldQuestionnaires, forms and document lists set for each case type.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partForeign nationals complete a self-service intake through the portal.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 LawLogix Immigration Case Management.
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. LawLogix Immigration Case Management 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 LawLogix Immigration Case Management 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 LawLogix Immigration Case Management is kept running until the checks on Litify are finished.

Where the data is now

A firm on LawLogix has its immigration cases in one product and, quite often, a client’s I-9 records in a sister product that is not part of the same data. The move is planned around the foreign national: who they are, who sponsors them, what has been filed and what expires when. Billing and accounting detail is confirmed in the analysis because the vendor does not publish it.

  1. The foreign national comes first

    Records are organised around the foreign national and then the employer, not around a client and a matter number. A law firm’s destination system will usually want the paying client at the top. The analysis sets which party becomes the client on each case and how the other is linked, so searches by either name still work.

  2. Guardian is a separate product

    LawLogix also sells Guardian for Form I-9 and E-Verify. Employers often hold both, and staff may speak of them as one system. I-9 records are not immigration case data and do not travel with it. The scope is written down at the start so nobody expects employment verification history to appear in the new case system.

  3. Workflows differ by case type

    Each case type has its own set of questionnaires, forms and documents to gather, delivered to the client as a personal checklist. A case in progress is partway through that list. What has been received and what is outstanding is carried as the status of each item, since a bare list of documents does not show what is missing.

  4. Two portals to replace

    Foreign nationals and employers each have a portal for answering questions, uploading documents and reading case updates. The portals are part of LawLogix and do not move. Everything already submitted is part of the case record and moves with it. How clients send documents after go-live is decided before cutover, and they are told once.

More about moving off LawLogix Immigration Case Management

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.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Litify, they get a rehearsed cutover of their own. 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 LawLogix Immigration Case Management and checking each trial against LawLogix Immigration Case Management.

  1. Analysis

    We read what LawLogix Immigration Case Management holds and how it is organised, then agree with you where each kind of record will sit in Litify. Anything with no place there stays behind or is archived, and you see which before the move.

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

  3. Trial load

    A trial is loaded into Litify and checked against LawLogix Immigration Case Management: 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.

  4. Cutover

    After a short freeze on changes in LawLogix Immigration Case Management, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. LawLogix Immigration Case Management 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 LawLogix Immigration Case Management 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 fromLawLogix Immigration Case Management
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 LawLogix Immigration Case Management 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

LawLogix Immigration Case Management to Litify: what firms ask

We know it as Edge. Is that the same system?

As far as the public record shows, yes. LawLogix’s immigration product has been listed and reviewed under the name Edge, and Equifax now calls it Immigration Case Management. The analysis starts from the firm’s own account and the screens staff use every day, so the name on the contract does not change the work.

Do the completed forms and receipt notices move?

They move as documents on each case, with their dates. The answers that produced the forms are data inside LawLogix and are mapped separately. Where the new system has matching fields the answers are loaded into them. Where it does not, the firm chooses between custom fields and a summary sheet filed on the matter.

What about our I-9 records in Guardian?

They are outside an immigration case migration. Guardian is a different product with its own data, and I-9 forms have their own retention rules. If an employer is changing I-9 systems too, that is planned as a separate piece of work with its own checks, and it should not share a cutover weekend.

Do trust balances in LawLogix Immigration Case Management 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 LawLogix Immigration Case Management 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 LawLogix Immigration Case Management have a place in Litify?

Most of it does on paper. Emails, notes, tasks, time entries, billing records, trust ledgers, the firm’s accounts 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 LawLogix Immigration Case Management data is loaded into Litify?

Templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, tasks, time entries, billing records, trust ledgers, the firm’s accounts 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.

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

LawLogix Immigration Case Management and Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from LawLogix Immigration Case Management 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.