Data migration route
Lead Docket data to Microsoft SQL Server
Lead Docket is a cloud CRM and intake system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Lead Docket holds and keeps it readable and open to queries.
Lead DocketCloud- Contacts: Exported in full
- Notes: Exported in full
- Tasks: Exported in full
- Billing: Exported in full
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Calendar: Confirmed in the analysis
- Trust money: Confirmed in the analysis
Microsoft SQL ServerServer- 5 carried
- 4 mapped
- 2 to confirm
What moves
What moves from Lead Docket to Microsoft SQL Server
Each row is a kind of record Lead Docket holds, whether Microsoft SQL Server 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 placePeople and companies, with their roles on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | Held in partIntake documents and files attached to a lead. | Has a place in partAs files in folders with an index table; storing files in the database is possible. | Exported with mapping |
| 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 partAs message files with an index table, or as rows of header fields. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | HeldNotes on each lead. | Has a placeRows of text linked to matters and contacts. | Exported in full |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeRows of appointments and key dates; nothing displays them as a calendar. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | HeldAutomated recurring tasks for each lead. | Has a placeRows with assignee, due date and status. | Exported in full |
| BillingInvoices, payments and debtor balances | Held in partPayment requests for consultation fees, retainers and referral fees. | Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeTransactions and balances for look-up; it is not a trust accounting system. | 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 placeAs added columns, or a table of field names and values. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | Held in partAutomated follow-up messages and custom intake scripts. | Has a place in partPrecedent files can be stored; automation does not run here. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldThe whole product: leads, sources, statuses, referrals and conversion. | Has a placeEnquiry rows, where the source recorded them. | Exported in full |
What the plans mean
- Exported in full
- Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Lead Docket.
- Exported with mapping
- Microsoft SQL Server 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 Lead Docket out to Microsoft SQL Server 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 Lead Docket 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.
Lead Docket is hosted by its maker and Microsoft SQL Server sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Lead Docket will release depends on its export tools, and that is confirmed in the analysis.
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 Microsoft SQL Server
There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.
Restored copy or rebuilt schema
Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.
No screens come with it
A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.
Documents sit beside the database
Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.
The edition follows the size
A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.
Backups and a test restore
An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.
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 Lead Docket holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Lead Docket 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 Microsoft SQL Server as a trial and checked against Lead Docket: record counts, totals where Lead Docket 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 Lead Docket, the export is run a final time and checked again. There is nothing to go live. Lead Docket 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 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 Microsoft SQL Server. 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
Microsoft SQL Server 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.
Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.
What is agreed and set up
- Server, instance and edition agreed with the IT provider
- Read-only logins and roles for named staff
- Views for matter, ledger, time and document look-ups
- Backup schedule and who tests a restore
- Plain names and descriptions for tables and columns
- Excel or Power BI connected for reporting
Questions
Lead Docket to Microsoft SQL Server: 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.
Does the copy in Microsoft SQL Server hold trust ledgers from Lead Docket?
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.
Does everything in Lead Docket have a place in Microsoft SQL Server?
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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.
What has to be decided before Lead Docket is written out to Microsoft SQL Server?
Documents, emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. Calendar entries and trust ledgers 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 Lead Docket and into Microsoft SQL Server
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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Lead Docket to Microsoft SQL Server?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.