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

Data migration route

Time Matters to Litify migration

Time Matters is a server-based 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.

FromTime MattersServer
  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. Emails: Carried with mapping
  8. Billing: Carried with mapping
  9. Custom fields: Carried with mapping
  10. Templates: Carried with mapping
  11. Notes: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
  13. Intake: Confirmed in the analysis
ToLitifyCloud
  • 6 carried
  • 4 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Time Matters to Litify

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

Records in Time Matters and their place in Litify
RecordIn Time MattersIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldHas a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldDocuments are created, searched and tied to clients and matters.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldEmails and attachments are managed against matters.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 and phone calls are separate records.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalled Events.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldCalled ToDos.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime and expenses.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeld in partBasic billing; advanced billing in the Billing Matters edition.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 itselfHeldForms, fields and record layouts are set by the firm.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeldMerge Templates, AutoEntry Forms, Triggers and Chains.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 Time Matters.
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 Time Matters 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 Time Matters, and kept as the record of what was billed and held.

Time Matters 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

Firms that have used Time Matters for years have usually reshaped it, and that is what takes thought when leaving. The standard records, which are contacts, matters, events, to-dos, notes, phone calls, emails and documents, move in a predictable way. What differs in every installation is the firm’s own forms, added fields, Triggers and Chains, and the analysis spends most of its time there.

  1. Forms the firm redesigned

    Record forms, field labels and layouts can be changed by the firm. A field that the default form calls one thing may carry a different label, and a different meaning, on the firm’s version. The mapping is made from the firm’s own form definitions, never from the default names.

  2. Triggers and Chains

    Triggers start tasks or events when a date or status changes, and Chains join steps into a sequence. AutoEntry Forms cut down repeated entry. The records they created come across, but the rules do not, so the processes that still matter are written down with the staff who use them and rebuilt in the destination.

  3. Every record type is separate

    Events, ToDos, phone calls, notes, emails and documents are distinct kinds of record, each tied to a matter or contact. Phone records in particular have no equivalent in many systems, and are loaded as dated notes. Counts for each record type are checked against Time Matters matter by matter.

  4. Billing may be elsewhere

    Time and expenses are recorded here, but invoices and ledgers may be kept in PCLaw or QuickBooks through a link, or in Billing Matters. The move identifies which, and treats that program as a second source. Matters are paired across the two using the reference the link relies on.

  5. Supported versions turn over

    The vendor retires versions on a published schedule, release by release, so a firm that has not upgraded for a few years may be on one that is out of support. It can still be moved. Its backup is checked early, since vendor help with a failed restore may not be on offer for a retired release.

More about moving off Time Matters

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

  1. Analysis

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

  4. Cutover

    Changes in Time Matters 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 Time Matters as at the cutover date. Time Matters 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 Time Matters 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 fromTime Matters
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 Time Matters 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

Time Matters to Litify: what firms ask

Do our documents come across with their matter links?

Each document in Time Matters has a record that ties it to a client or matter. The record supplies the matter, description and date, and the file supplies the content. Both are needed. Where a record refers to a file that has been moved or deleted, it is reported before the trial load.

Can we keep our custom fields?

The ones in use, yes, if the destination has custom fields for matters and contacts. Every field the firm added is listed in the analysis with how often it is filled. Fields that held structured data move as fields. Those used as scratch space usually become part of a note, by the firm’s choice.

We link Time Matters to PCLaw. Do they move together?

They should be planned together even if they go live a few days apart. The link keeps clients, matters and time in step between the two, and both feed the new system. One matter list is built from both, with PCLaw as the authority for money and Time Matters for the rest.

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

Most of it does on paper. Notes, trust ledgers 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 Time Matters 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, trust ledgers 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

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

Moving from Time Matters 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.