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

Data migration route

Litify data to Full data export

Litify is a cloud case management system, 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 Litify holds and keeps it readable and open to queries.

FromLitifyCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Documents: Exported in full
  4. Calendar: Exported in full
  5. Tasks: Exported in full
  6. Time and expenses: Exported in full
  7. Billing: Exported in full
  8. Emails: Exported with mapping
  9. Custom fields: Exported with mapping
  10. Templates: Exported with mapping
  11. Intake: Exported with mapping
  12. Notes: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToFull data exportFiles
  • 7 carried
  • 4 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Litify to Full data export

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

Records in Litify and their place in Full data export
RecordIn LitifyIn Full data exportWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters, with parties, calendar events, tasks, time and costs attached.Has a placeA matters table keyed by the original matter number.Exported in full
ContactsClients, other parties and referrersHeldParties, connected to intakes and matters through roles.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 systemHeldHeld in Litify’s document component, with tags, versions and templates.Has a placeFiles under their original names, in client and matter folders.Exported in full
EmailsEmails saved to matters or to the storeHeld in partEmails appear on the case activity timeline. Mailboxes stay in the mail system.Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them.Exported with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table with matter, author and date for each note.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendar events on the matter and the activity timeline.Has a placeA table of appointments and key dates; nothing shows it as a diary.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTasks, including those generated by matter plans.Has a placeA table of tasks with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTimekeeping, with time entries tied to the matter.Has a placeA time entries table with fee earner, matter, units, rate and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldBilling and eBilling, aimed chiefly at insurance defence work.Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them.Exported in full
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeA trust transactions table; ledger reports can be kept as PDF beside it.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a place in partJournals and account balances, where the source held a general ledger.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldFields are added through Salesforce configuration.Has a placeExtra columns under their original field names.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates with conditional logic. Matter plans automate tasks.Has a place in partTemplate files only; the merge fields in them will not run.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntakes with questionnaires, lead scoring and marketing source tracking.Has a place in partAn enquiries table, where the source tracked leads.Exported with mapping

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

Litify is hosted by its maker and Full data export 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 Litify will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

A firm leaving Litify is leaving a Salesforce environment that has usually been shaped by an implementation team and several years of administrators. Its data is all there and can be queried. The effort is in reading the configuration, separating Litify’s own objects from the firm’s additions, and collecting the documents, which are managed by a separate component.

  1. Parties and roles

    A person or company is a party, and a role ties that party to an intake or matter as client, defendant, insurer, provider or something the firm defined. One party can hold different roles on different matters. Roles are extracted with the party, so the destination gets one contact with its relationships and not a copy per matter.

  2. Intakes become matters

    An intake is its own record with a questionnaire and a status, converted to a matter when the client signs. Turned-down and referred-out intakes stay as intakes and can far outnumber matters in a high-volume practice. They are counted separately, and the firm decides how many go to the new system.

  3. Documents sit beside the records

    Files are managed by Docrio, Litify’s document component. How they are stored, and how a full copy is obtained, is established in the analysis. Records and files are generally extracted by different routes and joined on the matter. Counts are checked per matter after the join, including on closed matters.

  4. Injury detail in related records

    Plaintiff firms typically record damages, insurance, liens, negotiations and settlement figures in records related to the matter, and each firm names and extends them its own way. These lists are extracted as tables with the matter reference. Where the destination has no equivalent, each becomes a schedule saved to the matter.

  5. Automation stays behind

    Matter plans, flows and validation rules are Salesforce configuration. They explain why the data looks the way it does, for example why a field is always filled at a given stage, but they cannot be exported into another product. Each is documented and used as the specification for workflows in the destination.

More about moving off Litify

Where it is going

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.

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

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

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

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

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

More about moving into Full data export

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.

  1. Analysis

    We read what Litify holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Litify holds is in scope unless you take it out.

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

  3. Trial export

    The data is written to Full data export as a trial and checked against Litify: record counts, totals where Litify holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Litify, the export is run a final time and checked again. There is nothing to go live. Litify 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 Litify 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 fromLitify
Moving toFull data export

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

  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

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

Litify to Full data export: what firms ask

Do we need a Salesforce administrator to get our data out?

Someone with administrator access is needed, yes. The extraction reads the environment’s objects directly, and the administrator grants that access and explains what was customised. If the person who built it has left, the configuration is read from the system itself, which takes longer.

Are our documents included when Litify data is exported?

Do not assume so. Documents are managed by a separate component, and an export of matter records should not be expected to contain the files themselves. Both routes are covered in the plan and joined on the matter. A matter is only counted as moved when its files are attached to it.

We are moving to Litify. Who does the configuration?

Litify or one of its implementation partners normally configures the system. The migration fits into that project: the data mapping follows their design, and trial loads go into a test environment before production. It helps to agree early who owns the field list, because data and configuration change each other.

Does the copy in Full data export hold trust ledgers from 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 Litify before the plan is fixed.

Does everything in Litify have a place in Full data export?

Most of it does on paper. Notes, trust ledgers and the firm’s accounts 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 Litify is written out to Full data export?

Emails, custom fields, templates and intake records are exported with mapping, so each mapping is agreed with you first. Notes, trust ledgers and the firm’s accounts are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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

Litify and Full data export are the names and marks of their owners, used here only to identify the two systems.

Moving from Litify 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.