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

Data migration route

Firm Central to Litify migration

Firm Central is a cloud practice management system, and Litify is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

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

What moves

What moves from Firm Central to Litify

Each row is a kind of record Firm Central holds, whether Litify has a place for it, and what is planned. On this route six kinds of record carry across, one kind needs mapping and seven kinds are confirmed in the analysis.

Records in Firm Central and their place in Litify
RecordIn Firm CentralIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldOpen and closed matters with practice area, client group, permissions and primary attorney.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldClients, contacts and client groups.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldMatter folders that could be layered freely, plus a My Documents area for each user.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldMatter notes.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendar events, and Deadline Assistant events for firms that had that add-on.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldMatter tasks.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeld in partThrough the Time & Billing module, which was supplied by eBillity.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeld in partPre-bills, invoices and payments in the Time & Billing module.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 balancesHeld in partThe Time & Billing module had a Trusts & Retainers tab.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partEditions sold with Accounting had a chart of accounts and accounts payable.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields are created before loading.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt in Litify’s document generation.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLoaded as intakes.Confirmed in the analysis

What the plans mean

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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Litify. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Firm Central has to be given a case type in Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify is exported as reports and ledgers the firm can open without Firm Central, and kept as the record of what was billed and held.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Firm Central 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 Firm Central is kept running until the checks on Litify are finished.

Where the data is now

Firm Central was discontinued in 2024, so a move from it today starts with whatever the firm saved before the shutdown. Thomson Reuters’ extraction guide had firms download their data as a set of CSV files and zipped document bundles. The job is to find those files, work out what each contains, and rebuild matters from the pieces in a system the firm now uses.

  1. The source is an export

    What survives is a collection of downloads: contact and matter lists, document bundles and calendar files, saved by whoever ran the export in 2024. They may sit on one person’s computer. The analysis begins with an inventory of those files, including their dates, since an export taken weeks before the shutdown misses later work.

  2. One file per kind of record

    Matter lists, matter notes, matter tasks, billing rates, permissions and primary attorneys were each exported as their own CSV, and separately for open and closed matters. Each file is a flat list. The pieces are joined back together on the matter and client they name, and rows that match nothing are listed for the firm.

  3. Documents came out as zips

    Bulk document extraction produced zipped bundles holding each matter’s folders, with files in the format they were uploaded in. Firm Central allowed folders to be layered freely, so structures vary from matter to matter. Each user’s My Documents came out as a separate set and has no matter attached until someone assigns one.

  4. Billing sat with eBillity

    Time entries, invoices, payments and trust records were in the Time & Billing module, which eBillity supplied. Thomson Reuters told firms they could carry on with those eBillity products under a new billing arrangement. A firm that did so has its billing history in eBillity, not in the Firm Central export.

  5. What the export left out

    The guide notes that client portal messages could not be exported, and that links to Westlaw research saved in matter folders do not include the documents themselves. Neither can be recovered from the files. If either mattered to a particular matter, the firm’s email and Westlaw folders are the places to look.

More about moving off Firm Central

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 Firm Central and checking each trial against Firm Central.

  1. Analysis

    We read what Firm Central 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 Firm Central, 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 Firm Central: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Firm Central 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 Firm Central as at the cutover date. Firm Central 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 Firm Central 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 fromFirm Central
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 Firm Central 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

Firm Central to Litify: what firms ask

Firm Central has shut down. Is it too late to move our data?

Not if the firm ran the exports. Thomson Reuters gave firms a way to download contacts, matters, notes, tasks, calendar events and documents before the product ended. Those files can be cleaned and loaded into a current system. If no export was taken, what remains is whatever was also saved elsewhere.

We exported everything in 2024 but never loaded it anywhere. What can be done with it?

Quite a lot. The CSV files are joined back into matters with their contacts, notes and tasks, and the document bundles are unzipped and filed against the right matter. Before anything is made final, the firm sees a trial load and a list of whatever could not be matched.

Where did our time and billing records go?

They were never in the main Firm Central database. Time & Billing was an eBillity product offered through Thomson Reuters. Firms that kept it moved to a direct arrangement with eBillity. Those that did not would have downloaded invoices and reports before the end, and those downloads are the record.

Do trust balances in Firm Central 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 Firm Central 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 Firm Central have a place in Litify?

Most of it does on paper. Emails, notes, trust ledgers, the firm’s accounts, custom fields, templates and intake records 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 Firm Central data is loaded into Litify?

Billing records are carried with mapping, so each mapping is agreed with you first. Emails, notes, trust ledgers, the firm’s accounts, custom fields, templates and intake records 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

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

Moving from Firm Central 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.