Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Lead Docket to Litify migration

Lead Docket is a cloud CRM and intake system, and Litify is a cloud case management system. Contacts and intake history move, and open enquiries become leads or cases in Litify.

FromLead DocketCloud
  1. Contacts: Carried across
  2. Documents: Carried across
  3. Tasks: Carried across
  4. Intake: Carried across
  5. Emails: Carried with mapping
  6. Billing: Carried with mapping
  7. Custom fields: Carried with mapping
  8. Templates: Carried with mapping
  9. Notes: Confirmed in the analysis
  10. Calendar: Confirmed in the analysis
  11. Trust money: Confirmed in the analysis
ToLitifyCloud
  • 4 carried
  • 4 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Lead Docket to Litify

Each row is a kind of record Lead Docket holds, whether Litify has a place for it, and what is planned. On this route four kinds of record carry across, four kinds need mapping and three kinds are confirmed in the analysis.

Records in Lead Docket and their place in Litify
RecordIn Lead DocketIn LitifyWhat is planned
ContactsClients, other parties and referrersHeldLeads and referral partners.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeld in partIntake documents and files attached to a lead.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeld in partFollow-up emails and texts sent from the product are kept with the lead.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeldNotes on each lead.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events on the matter.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeldAutomated recurring tasks for each lead.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeld in partPayment requests for consultation fees, retainers and referral fees.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 balancesTo be confirmedTo be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom intake forms with the firm’s own qualifying fields.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partAutomated follow-up messages and custom intake scripts.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldThe whole product: leads, sources, statuses, referrals and conversion.Has a placeLoaded as intakes.Carried across

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against Lead Docket.
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

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 Litify 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 Litify 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 Litify are finished.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off Lead Docket

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into Litify

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 Lead Docket and checking each trial against Lead Docket.

  1. 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 Litify. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. 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.

  3. Trial load

    The data is loaded into Litify 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.

  4. Cutover

    Changes in Lead Docket 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 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

Step 1 of 5: Start with the route

Moving fromLead Docket
Moving toLitify

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Lead Docket 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.

  3. 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

Lead Docket to Litify: 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 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 Lead Docket 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 Lead Docket have a place in Litify?

Most of it does on paper. Notes, 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 Litify 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 Litify?

Emails, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes, 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.

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.

How we do itDiscovery to rollout, step by step

Lead Docket and Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Lead Docket 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.