Data migration route
Curo365 to Litify migration
Curo365 is a cloud practice management system, and Litify is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
Curo365Cloud- 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
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Templates: Confirmed in the analysis
LitifyCloud- 7 carried
- 3 mapped
- 4 to confirm
What moves
What moves from Curo365 to Litify
Each row is a kind of record Curo365 holds, whether Litify has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldClient records and relationships are held in Dynamics 365. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldManaged in SharePoint. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partMail stays in Exchange and Outlook; what is filed to a matter was not confirmed. | 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 | To be confirmed | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldCalendars are Exchange and Outlook. | Has a placeCalendar events on the matter. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partAutomated workflows for firm processes; task records were not confirmed. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime can be entered from Outlook. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldBilling and invoicing are part of the product. | 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 | To be confirmed | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | Held in partKept in Microsoft Business Central or QuickBooks, not inside Curo365 itself. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldBuilt on Dynamics 365, where a firm can add its own fields. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt in Litify’s document generation. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partClient management and marketing use Dynamics 365 CRM functions. | 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 Curo365.
- 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
Matters become cases. The ledgers need a home.
Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Litify. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.
Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Curo365 has to be given a case type in Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify is exported as reports and ledgers the firm can open without Curo365, and kept as the record of what was billed and held.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Curo365 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 Curo365 is kept running until the checks on Litify are finished.
Where the data is now
Leaving Curo365
Curo365 is one product on the screen and several Microsoft services underneath. Matters are in Dynamics 365, documents in SharePoint, email and diaries in Exchange, the ledger in Business Central or QuickBooks. Leaving it means collecting from each of those and putting the links back together. The documents and mail are in the firm’s own Microsoft 365, which changes what has to move at all.
Four places, one matter
A single matter has its details in Dynamics 365, its files in SharePoint, its emails and appointments in Outlook and its money in the accounting package. Each is extracted separately and joined on the matter number. The first trial load is mainly a test of that join: does every document folder find its matter.
Documents may not need moving
The files are in SharePoint in the firm’s Microsoft 365. If the new system can work with SharePoint, they can stay where they are and be linked. If it has its own document store, they are copied in with their folder structure and dates. That choice is the largest single factor in the size of the job.
The ledger is beside it
Accounting is done in Microsoft Business Central or in QuickBooks, so the general ledger and payables are taken from that package and not from Curo365. Billing history and the debtor ledger are compared before cutover so that both agree on what each client owes. Where client money is recorded is confirmed in the analysis.
Calendars belong to mailboxes
Appointments are ordinary Outlook items in each person’s mailbox, and they remain there after the move. What can be lost is the link from an appointment to its matter. Court dates and limitation dates are identified and loaded into the new system’s own calendar, so they do not depend on one lawyer’s mailbox.
Power BI reports
Partners often run the firm from Power BI dashboards that read Curo365 data. A dashboard is not a record and cannot be migrated. The reports people open each week are listed, with the figures each one shows, and rebuilt against the new system or replaced by its own reporting.
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 Curo365 and checking each trial against Curo365.
Analysis
We read what Curo365 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 Curo365, 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 Curo365: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Curo365 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 Curo365 as at the cutover date. Curo365 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 Curo365 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 Curo365 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
Curo365 to Litify: what firms ask
Our documents are already in SharePoint. Do we have to move them?
Not always. They are in the firm’s own Microsoft 365 and remain there whatever happens to the practice system. If the destination can link to SharePoint, the folders are re-attached to the new matters. If it stores documents itself, they are copied across and the SharePoint library is kept read only for a period.
We have customised Curo365 heavily. Does that complicate a move?
It adds work, and the work is predictable. Dynamics 365 lets a firm add fields, tables and workflows, and those additions are visible in the configuration. The analysis lists each one with how many records use it. Fields with real data are mapped. Workflows are described in plain words so they can be rebuilt or dropped.
Will entering time from Outlook still work?
The entries already made are in Curo365 and move as time records, billed and unbilled. Entering time from Outlook afterwards depends on whether the new system has an Outlook add-in of its own. That is confirmed for the chosen destination in the analysis, and fee earners are shown the new method before go-live.
Do trust balances in Curo365 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 Curo365 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 Curo365 have a place in Litify?
Most of it does on paper. Notes, trust ledgers, the firm’s accounts and templates 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 Curo365 data is loaded into Litify?
Emails, billing records and custom fields are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers, the firm’s accounts and templates 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 Curo365 and into Litify
Other destinations from Curo365
Other systems that move 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.
Curo365 and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from Curo365 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.