Data migration route
CollectMax to Litify migration
CollectMax is a server-based case management system for debt recovery work, and Litify is a cloud case management system. The records line up case for case, and the detail is in the fields and stages.
CollectMaxServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Tasks: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Intake: Confirmed in the analysis
LitifyCloud- 4 carried
- 3 mapped
- 7 to confirm
What moves
What moves from CollectMax to Litify
Each row is a kind of record CollectMax holds, whether Litify has a place for it, and what is planned. On this route four kinds of record carry across, three kinds need mapping and seven kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldAccounts, each with one or more claims, a status code and links to related accounts. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldDebtors, clients (creditors or forwarders), plaintiffs and other account members. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partLetters and documents are generated per account or claim; stored files not confirmed. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has 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 notes | HeldAccount notes, with colour-coded note indicators. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeCalendar events on the matter. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partMaxPlans schedule the documents due on each account. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a placeTime entries on the matter. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | HeldCollection fee and suit fee invoices to clients, produced by remittance processing. | 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 | HeldA trust bank account with internal client accounts, monitored against overdraft. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | Held in partTrust and firm operating bank accounts for collections; a general ledger was not confirmed. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partClient-specific user variables and firm-defined status codes. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldLetter and document templates, sent singly or in batches. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeLoaded as intakes. | Confirmed in the analysis |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against CollectMax.
- 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. CollectMax 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.
CollectMax runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Litify is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving CollectMax
A collections system does not look like a practice system. There is no matter with a client and a bill. There is an account with debtors and claims, a balance that grows with interest, payments that land in trust and a remittance that pays the client. Moving off it means deciding what a matter is before a single record is mapped.
Accounts, debtors and claims
One CollectMax account can hold several debtors and several claims, and each claim has a reference number that is usually the original creditor’s account number. A destination needs one matter per account or one per claim. The choice affects how balances, documents and court details divide, so it is tested on real accounts before it is fixed.
Five-part claim balances
A debt is kept as principal, interest, fees, costs and other, and interest can be projected forward. A general practice system has a debtor balance on an invoice and nothing like this. If the destination cannot calculate interest on a claim, the balance at cutover is loaded as a fixed figure with the rate and date noted.
Remittance, not billing
Debtor payments go into the trust bank account. Remittance processing then pays the client and raises the firm’s invoice for its collection fee, under whichever withholding arrangement that client has. This is the reverse of ordinary legal billing. Each client’s arrangement is recorded in the analysis, since the new system has to reproduce the same split.
Client, forwarder and plaintiff
The client on an account is either the creditor or a forwarder who sent the debt on, and a plaintiff may be attached separately. Three parties can stand where a practice system expects one client. All three are kept as linked contacts, and the one the firm reports and remits to becomes the client.
Status codes and contact flags
Status codes show where each claim is in the collection process and when it changed. Accounts also carry flags such as Do Not Contact, bankruptcy or a defending attorney, which stop letters being produced. Those flags protect the firm from contacting someone it must not. They are mapped first and checked on every trial load.
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 CollectMax and checking each trial against CollectMax.
Analysis
We read what CollectMax 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 CollectMax, 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 CollectMax: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in CollectMax 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 CollectMax as at the cutover date. CollectMax 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 CollectMax 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 CollectMax 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
CollectMax to Litify: what firms ask
Can a general practice system run a collections practice?
Only with work. Matters, contacts and documents are no trouble. Interest on claims, payment posting in bulk, remittance to clients and electronic exchange with creditors are collections functions that most general systems lack. The analysis lists which of these the firm uses daily, and that list usually settles what kind of destination is realistic.
What happens to accounts with payment arrangements in progress?
They are the records to watch. Each has a balance, a payment history and a next expected payment. Where the destination takes payment history, it is loaded so the balance can be recalculated, not just stated. On the trial load, a sample of paying accounts is compared with CollectMax, including interest accrued to the day.
Do trust balances for each client carry over?
They are carried as opening balances, client by client. CollectMax keeps many clients’ money in one trust bank account through internal accounts, and the total of those must equal the bank balance on cutover day. That reconciliation is rehearsed on a full trial load first, because the financial cutover is not something to repeat.
Do trust balances in CollectMax 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 CollectMax 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 CollectMax have a place in Litify?
Most of it does on paper. Emails, notes, calendar entries, time entries, trust ledgers, the firm’s accounts and intake records 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 CollectMax data is loaded into Litify?
Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, calendar entries, time entries, trust ledgers, the firm’s accounts and intake records 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 CollectMax 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.
CollectMax and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from CollectMax 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.