Data migration route
CollectMax data to Full data export
CollectMax is a server-based case management system for debt recovery work, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what CollectMax holds and keeps it readable and open to queries.
CollectMaxServer- Matters: Exported in full
- Contacts: Exported in full
- Documents: Exported in full
- Notes: Exported in full
- Tasks: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Firm accounts: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Emails: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Intake: Confirmed in the analysis
Full data exportFiles- 7 carried
- 3 mapped
- 4 to confirm
What moves
What moves from CollectMax to Full data export
Each row is a kind of record CollectMax holds, whether Full data export 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 | HeldAccounts, each with one or more claims, a status code and links to related accounts. | Has a placeA matters table keyed by the original matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldDebtors, clients (creditors or forwarders), plaintiffs and other account members. | Has a placeA contacts table and a table of each contact’s role on each matter. | Exported in full |
| 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 placeFiles under their original names, in client and matter folders. | Exported in full |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldAccount notes, with colour-coded note indicators. | Has a placeA notes table with matter, author and date for each note. | Exported in full |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeA table of appointments and key dates; nothing shows it as a diary. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partMaxPlans schedule the documents due on each account. | Has a placeA table of tasks with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a placeA time entries table with fee earner, matter, units, rate and billed status. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | HeldCollection fee and suit fee invoices to clients, produced by remittance processing. | Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldA trust bank account with internal client accounts, monitored against overdraft. | Has a placeA trust transactions table; ledger reports can be kept as PDF beside it. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | Held in partTrust and firm operating bank accounts for collections; a general ledger was not confirmed. | Has a place in partJournals and account balances, where the source held a general ledger. | Exported with mapping |
| Custom fieldsFields and record types the firm added itself | Held in partClient-specific user variables and firm-defined status codes. | Has a placeExtra columns under their original field names. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldLetter and document templates, sent singly or in batches. | Has a place in partTemplate files only; the merge fields in them will not run. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a place in partAn enquiries table, where the source tracked leads. | Confirmed in the analysis |
What the plans mean
- Exported in full
- Full data export has a place for this kind of record. It is loaded there and checked against CollectMax.
- Exported with mapping
- Full data export 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
Not a new system. A complete copy the firm can query.
Writing CollectMax out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in CollectMax as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in CollectMax stays untouched until the copy in Full data export has been checked.
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 Full data export
A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.
Tables that still join up
Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.
Documents with an index
Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.
Reports a person can read
Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.
What an export does not keep
Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.
Checked while the source is open
Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what CollectMax holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything CollectMax holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Full data export as a trial and checked against CollectMax: record counts, totals where CollectMax holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in CollectMax, the export is run a final time and checked again. There is nothing to go live. CollectMax is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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 Full data export. 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
Structure, permissions and handover
Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.
What is agreed and set up
- Folder layout for tables, documents and reports
- What the key to tables, columns and identifiers records
- Where the copies are stored and who is custodian
- Who may open it, as approved by a partner
- Which look-ups staff must be able to do unaided
- Retention period and the date it is next reviewed
Questions
CollectMax to Full data export: 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.
Does the copy in Full data export hold trust ledgers from CollectMax?
Yes. A trust transactions table; ledger reports can be kept as PDF beside it. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in CollectMax as at the export date.
Does everything in CollectMax have a place in Full data export?
Most of it does on paper. Emails, calendar entries, time entries 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 Full data export is kept as a readable archive, and you see which before the move.
What has to be decided before CollectMax is written out to Full data export?
The firm’s accounts, custom fields and templates are exported with mapping, so each mapping is agreed with you first. Emails, calendar entries, time entries and intake records are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from CollectMax and into Full data export
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 Full data export are the names and marks of their owners, used here only to identify the two systems.
Moving from CollectMax to Full data export?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.