Data migration route
Lead Docket to Neos migration
Lead Docket is a cloud CRM and intake system, and Neos is a cloud case management system for personal injury work. Contacts and intake history move, and open enquiries become leads or cases in Neos.
Lead DocketCloud- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Tasks: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Calendar: Confirmed in the analysis
- Trust money: Confirmed in the analysis
NeosCloud- 5 carried
- 4 mapped
- 2 to confirm
What moves
What moves from Lead Docket to Neos
Each row is a kind of record Lead Docket holds, whether Neos has a place for it, and what is planned. On this route five kinds of record carry across, four kinds need mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldLeads and referral partners. | Has a placeParties, providers and case contacts. Contacts can be imported from CSV. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partIntake documents and files attached to a lead. | Has a placeCase Docs tab, organised in sub-tabs. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partFollow-up emails and texts sent from the product are kept with the lead. | Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldNotes on each lead. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeCase calendar entries. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | HeldAutomated recurring tasks for each lead. | Has a placeLoaded as checklist items. | Carried across |
| BillingInvoices, payments and debtor balances | Held in partPayment requests for consultation fees, retainers and referral fees. | Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom intake forms with the firm’s own qualifying fields. | Has a placeUser-defined fields are created on the relevant tab first. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partAutomated follow-up messages and custom intake scripts. | Has a place in partTemplates are rebuilt for Neos document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldThe whole product: leads, sources, statuses, referrals and conversion. | Has a placeIntakes tab. Simple intake imports from CSV are supported. | Carried across |
What the plans mean
- Carried across
- Neos has a place for this kind of record. It is loaded there and checked against Lead Docket.
- Carried with mapping
- Neos 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
Intake history moves. The pipeline is rebuilt.
Intake data is the front end of a case. A lead in Lead Docket carries the first conversation, the screening answers, the referrer and often a signed retainer. Many case management systems have an intake stage of their own, so a lead can land as a prospective case with that history attached. Where Neos has no such stage, open enquiries are loaded as contacts with their status in a note, and the firm decides which to open as cases.
Screening questions are the mapping work. Each intake form is a set of fields, and each field has to find a place on the case or be kept as a note. Referral sources are tidied into one list first, because they are usually typed by hand and reporting depends on them. Marketing automations, email sequences and web forms do not move as data. They are set up again in Neos or in the tool that feeds it.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Lead Docket 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 Lead Docket is kept running until the checks on Neos are finished.
Where the data is now
Leaving Lead Docket
Moving off Lead Docket is a move of leads, not matters. The questions are how much history the firm wants, and where it goes. Signed leads already exist as cases elsewhere. What remains is the pipeline in progress, the declined and referred-out enquiries, and the marketing history that the firm’s spending decisions rest on.
Leads are not matters
A lead has a status, a source and intake answers, but no matter number or ledger. Loading every lead into a practice system as a matter fills it with enquiries that never became work. Open leads go to the destination’s intake module, and declined ones become contacts with a note or stay in an export.
Marketing source and spend
Each lead carries the source it came from, and the firm enters spend against its campaigns so the return can be reported. That history is only useful if the source names survive unchanged. The source list is tidied first, and the old reports are exported so last year’s figures can still be compared.
Referral fees still owed
Leads referred to other firms are tracked with their fees, and the product checks in with referral partners automatically. Some of those fees are still to come when the firm moves. Each open referral is listed with partner, client and expected fee, and loaded where someone will keep following it up.
Intake answers on custom forms
Intake scripts are custom to each firm, so the answers sit in fields the firm designed. For signed clients those answers will usually have been passed to the case system already. Answers on open leads are mapped to the new intake form question by question, with anything unmatched kept as a note.
Duplicates with the case system
A signed lead exists twice: once here and once as a client in the case management system. If both are loaded into one new system, every client appears twice. The two are matched on the link between them or on name and phone, and the case record is treated as the master.
Where it is going
Arriving in Neos
Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.
Every figure needs a value code
Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.
Lists are set up first
Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.
Documents go to sub-tabs
Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.
Reminders split two ways
Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.
Assembly runs its own conversions
Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.
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 Neos 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 Lead Docket and checking each trial against Lead Docket.
Analysis
We read what Lead Docket holds and how its records link, then agree with you, field by field, where each piece will sit in Neos. 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 Lead Docket, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Neos as a trial and checked against Lead Docket: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Lead Docket are frozen for an agreed window, the data is collected a final time and Neos 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 Lead Docket as at the cutover date. Lead Docket 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 Lead Docket 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 Lead Docket holds
What is in it, how its records link, and where each piece would sit in Neos. 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 Neos
Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.
Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.
Set-up decisions in Neos
- Set case types, statuses and staff roles
- Agree the value code list with accounts staff
- Build checklists for each case type and stage
- Create user-defined fields for data the tabs lack
- Prepare document templates for the generation wizard
- Connect Microsoft 365, QuickBooks and the phone system
Questions
Lead Docket to Neos: what firms ask
Should our declined leads move to the new system?
Often not as live records. Declined enquiries matter for conflict checks and for marketing numbers, and neither needs them cluttering the intake screen. One arrangement is to load the contact with a one-line reason and keep the full export on file. Firms with strict conflict rules load more.
We are leaving Filevine as well. Does Lead Docket have to go?
Not necessarily. Lead Docket connects to case management software other than Filevine, so it can stay if the new system is one it works with or can accept leads another way. If the destination has its own intake module, running one tool is simpler, and the open pipeline is moved across at the same cutover.
Can the marketing reports be recreated?
The figures can, if source and spend come across cleanly. Reports are rebuilt in the destination’s own reporting or in a spreadsheet fed from it. Historic periods are exported from Lead Docket before the move, because rebuilding several years of conversion history inside a new system is seldom needed.
Do trust balances in Lead Docket have a place in Neos?
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 Lead Docket before the plan is fixed. If Neos 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 Lead Docket have a place in Neos?
Most of it does on paper. Calendar entries and trust ledgers 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 Neos is kept as a readable archive, and you see which before the move.
What has to be decided before Lead Docket data is loaded into Neos?
Emails, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Calendar entries and trust ledgers 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 Lead Docket and into Neos
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.
Lead Docket and Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from Lead Docket to Neos?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.