Data migration route
eimmigration by Cerenade to Litify migration
eimmigration by Cerenade 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.
eimmigration by CerenadeCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
LitifyCloud- 7 carried
- 4 mapped
- 3 to confirm
What moves
What moves from eimmigration by Cerenade to Litify
Each row is a kind of record eimmigration by Cerenade holds, whether Litify has a place for it, and what is planned. On this route seven kinds of record carry across, four kinds need mapping and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases, each with a petition type, assigned forms, process steps and receipt numbers. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldClient profiles with biographic, family and employment history, plus prospects and leads. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldStored on client and case profiles; clients upload through the portal. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails can be logged on client and case profiles; texts and portal messages are kept too. | 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 notes | HeldClient interaction notes, which can be shown to the client in the portal. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldAppointments and caseworker calendars, with Office 365 or Google Calendar sync. | Has a placeCalendar events on the matter. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldProcess steps, reminders and automated workflows for each case type. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldCaseworker time tracked against each case and client profile. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldInvoices, payment plans, expenses and payments. | 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 balances | HeldThe vendor describes built-in trust accounting. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields on client and case profiles. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldGovernment forms library, multilingual questionnaires, email and letter templates. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads and prospects pipeline, website enquiry capture and intake questionnaires. | 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 eimmigration by Cerenade.
- 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. eimmigration by Cerenade 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 eimmigration by Cerenade 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 eimmigration by Cerenade is kept running until the checks on Litify are finished.
Where the data is now
Leaving eimmigration by Cerenade
Moving off eimmigration is mostly a question of where a very detailed client record goes. The system holds far more about each person than a general practice system has fields for, and it ties that data to government forms. Cases, documents, invoices and trust balances have ordinary homes. The biographic data, the questionnaires and the form answers need a decision each.
A profile deeper than a contact
Each client profile carries biographic, family, professional and historical data, plus copies of passports, I-94s and birth certificates. A general practice system gives a contact a name, an address and a few custom fields. The analysis lists every profile field in use and decides which become custom fields, which become a summary document on the matter, and which stay behind.
Forms are data, not files
The government forms are filled from answers held in the system, so one address change updates every form. Outside an immigration product those answers have no engine to feed. Filed forms are carried as PDFs on the case. The answers behind them move only where the destination has a matching field or its own forms library.
Expiry dates and receipt numbers
Cases are found by receipt or notice number, and the system watches passport, visa and I-94 expiry dates up to 180 days ahead. Those dates are worth more than most of the record. Each one needs a date field in the new system that can raise a reminder, because a date sitting inside a note warns nobody.
Family members share a file
The system shows every case and service for a client together with their associated family members. A spouse and children on one petition are separate people linked to one another. The links are checked in the trial load by opening known families and confirming that each member still reaches the same cases.
Payment plans and trust
Invoices, payment plans, expenses and trust accounting are inside the product, with card payments taken through Braintree or LawPay. A client halfway through a payment plan has a schedule and a balance. The balance moves as an opening figure. The schedule and any automatic card payments are set up again in the new system before the old ones are switched off.
Where it is going
Arriving in Litify
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.
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.
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.
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.
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.
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.
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 eimmigration by Cerenade and checking each trial against eimmigration by Cerenade.
Analysis
We read what eimmigration by Cerenade 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.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in eimmigration by Cerenade, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Litify as a trial and checked against eimmigration by Cerenade: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in eimmigration by Cerenade 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 eimmigration by Cerenade as at the cutover date. eimmigration by Cerenade 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 eimmigration by Cerenade 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 eimmigration by Cerenade 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.
- 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
eimmigration by Cerenade to Litify: what firms ask
Will our clients’ immigration forms come across as forms?
As documents, yes. Each completed form is carried as a PDF on the client’s case. As live forms that refill from the client’s data, only if the new system is an immigration product with its own forms library. Which of the two applies to your destination is settled in the analysis, before anything is extracted.
What happens to the client portal?
Portal logins do not move. What clients put there does: uploaded documents, questionnaire answers and the notes you chose to show them are all part of the case record. If the new system has a portal, clients are invited to it after cutover, and the firm decides what they should see on day one.
Can we bring archived and closed cases?
Yes. eimmigration keeps active, archived and closed cases apart, and each status is carried across as it stands. Immigration clients come back years later for a renewal or a naturalisation, which is a reason to bring every case. If older ones are left behind, they remain in the read-only copy of the old system.
Do trust balances in eimmigration by Cerenade 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 eimmigration by Cerenade 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 eimmigration by Cerenade have a place in Litify?
Most of it does on paper. Notes, trust ledgers and the firm’s accounts 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 eimmigration by Cerenade data is loaded into Litify?
Emails, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers and the firm’s accounts are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from eimmigration by Cerenade and into Litify
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.
eimmigration by Cerenade and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from eimmigration by Cerenade 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.