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

Data migration route

Liberate to Litify migration

Liberate is a 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.

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

What moves

What moves from Liberate to Litify

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

Records in Liberate and their place in Litify
RecordIn LiberateIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldElectronic matters holding data, documents and emails.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersTo be confirmedHas a placeLoaded as parties and connected by roles.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldTags and definable document categories, with version control.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldEmails are held on the matter; time spent in Outlook can be recorded.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 notesTo be confirmedTo 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 peopleHeld in partAuthorisation workflows and business process automation.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldIncludes automatic time recording.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldOne-click and scheduled billing, with credit control procedures.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
Firm accountsGeneral ledger, office account and payablesHeldPurchase ledger, supplier database and built-in financial reporting.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 automationHeldPrecedents and document templates filled with matter data.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
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 Liberate.
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 Liberate 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 Liberate, and kept as the record of what was billed and held.

How Liberate is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Liberate runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Litify is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

Linetime sells Liberate to larger firms, which tend to have high matter volumes and an accounts department that runs credit control inside the system. Customisation by Linetime is part of the offer. A move therefore begins with an inventory of what was changed for this firm, and with the accounts team, whose billing schedules, credit control procedures and purchase ledger all have to be closed off or carried over.

  1. Customised for the firm

    Linetime offers customisation to meet a firm’s own needs, and long-standing clients may have screens, fields and processes built for them. Those additions are not in any manual. We ask the firm and the vendor for a list, then confirm it against the database, so a field built only for this firm is not missed.

  2. Categories and tags, not folders

    Documents are organised by tags and by categories the firm defines. A matter’s documents may never have been in a folder. For a destination that files by folder, the category becomes the folder name, tags are carried as metadata where the new system has it, and uncategorised documents are placed in a general folder for review.

  3. Documents under version control

    Liberate keeps documents under version control. A migration normally takes the latest version of each document. Where the firm needs earlier drafts, we establish how Liberate stores them and whether the destination has its own versioning to receive them, then test on a matter with a long drafting history.

  4. Credit control procedures

    Credit control is run inside Liberate, with procedures that can be set at client and matter level. An unpaid bill may be part-way through a chasing sequence at cutover. The debtor balances move as figures. Alongside them, the stage each debt has reached is exported as a list so the accounts team can pick up the chase.

  5. Scheduled bills in progress

    Billing can be scheduled, so some clients are billed automatically on set dates. Those schedules do not transfer. They are listed before cutover with their amounts and dates, the last scheduled run is completed in Liberate, and the equivalent arrangement is set up in the new system before the next one falls due.

More about moving off Liberate

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

  1. Analysis

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

  4. Cutover

    Changes in Liberate 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 Liberate as at the cutover date. Liberate 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 Liberate 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 fromLiberate
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 Liberate 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

Liberate to Litify: what firms ask

How do we find out what was customised for us?

Start with the people who asked for it: accounts, department heads, IT. Linetime’s records of development work for the firm help as well. We then compare the firm’s database with the list, looking for tables and fields that hold data but appear in nobody’s account, and ask what they were for.

Does our purchase ledger move?

Only if the new system, or an accounting package beside it, has a purchase ledger. Supplier records and unpaid supplier invoices are extracted and loaded there as opening items. Paid history stays in the archive. A firm moving to a product without office accounts decides on its accounting package during the analysis.

Can the move be staged by department?

Case data can sometimes be staged. Accounts cannot be split easily, because billing and the ledgers for the whole firm sit in one system. Running two systems also means two places to check conflicts. Most firms move everything in one cutover and stage the training instead.

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

Most of it does on paper. Contacts, notes, calendar entries, trust ledgers, the firm’s accounts, custom fields 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 Liberate data is loaded into Litify?

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

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

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