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

Data migration route

CosmoLex to Litify migration

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

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

What moves

What moves from CosmoLex to Litify

Each row is a kind of record CosmoLex holds, whether Litify 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 CosmoLex and their place in Litify
RecordIn CosmoLexIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach has a Matter File #, an area of law and a matter owner.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldClients and other contacts; payees for accounts payable are a separate list.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldBuilt-in storage, or OneDrive, Google Drive, Dropbox, Box or NetDocuments linked by matter.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails sent to the firm’s forwarding address are tagged to matters by sender or recipient.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 notesHeldTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldHas a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTask workflows can be loaded into new or existing matters.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldEntries are called timecards.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldHas 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 balancesHeldTrust ledgers, journals and three-way reconciliation reports.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger with chart of accounts, bank feeds, accounts payable and cheque printing.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom fields can be used as merge fields in documents.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeldTemplates are Word documents using merge fields downloaded from CosmoLex.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partIntake forms are included; the vendor also describes lead tracking.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 CosmoLex.
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 CosmoLex 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 CosmoLex, 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 CosmoLex 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 CosmoLex is kept running until the checks on Litify are finished.

Where the data is now

Leaving CosmoLex is rarely just a practice management change. For most firms it is also the day their accounting system changes, since the general ledger, bank reconciliations and trust records are all inside. The matters and documents are planned in the usual way. A harder conversation is the one with the bookkeeper and accountant about where the books go next and on what date.

  1. One ledger for everything

    Billing posts straight to the general ledger, on a cash or accrual basis the firm chose at set-up. The books are not in a separate package that carries on unchanged. A destination with lighter accounting means a new package for the books, and trial balances from both are compared at the cutover date.

  2. Reconciliations stay behind

    Bank feeds, matched transactions and completed reconciliation statements are a record of work done, not data another system can load. Before cutover the firm runs and saves the reconciliation and three-way reports for every period it may be asked about, and the read-only copy of CosmoLex is kept as the fall-back record.

  3. Inactive means settled

    A matter can only be made inactive once its trust funds are disbursed, and on accrual accounting once its receivable is cleared. So an active matter is not always a live one. Some are finished files still holding money. They are listed for the firm, because the destination will treat them as open.

  4. Emails tagged by address

    Forwarded emails are tagged to a matter when the sender or recipient matches an email address on the client record, and land in a Tagged folder. Where there is no match, or more than one, the email waits for someone to file it. That untagged pile is either cleared or knowingly left behind before extraction.

  5. Law society records in Canada

    The Canadian edition produces law society compliance reports such as the clients’ general journal and general receipts journal. A Canadian firm needs those reports complete to the cutover date and stored where they can be produced on request. The destination’s own reports only start from the opening balances.

More about moving off CosmoLex

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

  1. Analysis

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

  4. Cutover

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

CosmoLex to Litify: what firms ask

We are on CosmoLex Classic and are being moved to NextGen. Should we wait before changing systems?

It makes little difference to the data. The vendor describes NextGen as the same core functions with a new interface, and the firm’s records carry over. If a move away is already decided, the analysis can be done on whichever version the firm is using on the day.

Can our Word templates be reused?

The documents themselves can. CosmoLex templates are ordinary Word files that use mail merge fields taken from a CosmoLex field list. In a new system the wording and layout survive, and each merge field is replaced with the destination’s equivalent. Fields based on custom data take the longest to match.

How far back does the financial history go across?

That is a choice. Some destinations accept historic invoices, payments and trust transactions as records. Others start from opening balances, with older detail left in the read-only CosmoLex copy and in saved reports. Whichever is chosen, a complete trial load is run first so the trust and ledger figures can be agreed before the real cutover.

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

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 Litify is kept as a readable archive, and you see which before the move.

What has to be decided before CosmoLex 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 the firm’s accounts 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

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

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