Data migration route
Lead Docket to Filevine migration
Lead Docket is a cloud CRM and intake system, and Filevine is a cloud case management system. Contacts and intake history move, and open enquiries become leads or cases in Filevine.
Lead DocketCloud- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Tasks: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Intake: Carried with mapping
- Calendar: Confirmed in the analysis
- Trust money: Confirmed in the analysis
FilevineCloud- 5 carried
- 4 mapped
- 2 to confirm
What moves
What moves from Lead Docket to Filevine
Each row is a kind of record Lead Docket holds, whether Filevine 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 placeContact cards, linked to projects. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partIntake documents and files attached to a lead. | Has a placeDocs section with folders. Templated project folders can be set per type. | 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 placeHeld in the activity feed of the project. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldNotes on each lead. | Has a placeHeld as notes in the activity feed. | Carried across |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeDeadlines and calendar events. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | HeldAutomated recurring tasks for each lead. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | Held in partPayment requests for consultation fees, retainers and referral fees. | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. | 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 placeCustom sections and fields per project type. | 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 as Filevine document templates. They are not converted. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldThe whole product: leads, sources, statuses, referrals and conversion. | Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine. | Carried with mapping |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Lead Docket.
- Carried with mapping
- Filevine 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.
Lead Docket and Filevine are related: they share a maker, or one is built on the other. Where a maker offers its own path between two of its products, that path is looked at first, and the analysis establishes what it carries and what it leaves. The points below apply wherever the two differ.
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 Filevine 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 Filevine 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 Filevine 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 Filevine
Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.
Project types before data
Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.
One contact card per person
Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.
Lists become collection items
Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.
History goes into the feed
File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.
Billing is a separate switch
The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
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 Filevine. 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 Filevine 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 Filevine 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 Filevine. 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 Filevine
Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.
Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.
Set-up decisions in Filevine
- Design project types, sections and fields for each practice area
- Define phases and the tasks each phase should trigger
- Build document templates that fill from project fields
- Set teams, permissions and protected sections for restricted matters
- Decide whether Billing and Payments are switched on
- Connect Lead Docket so signed leads become projects
Questions
Lead Docket to Filevine: 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 Filevine?
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 Filevine 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 Filevine?
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 Filevine 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 Filevine?
Billing records, custom fields, templates and intake records 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 Filevine
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 Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Lead Docket to Filevine?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.