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

Data migration route

Mitratech CaseCloud to Litify migration

Mitratech CaseCloud 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.

FromMitratech CaseCloudCloud
  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
ToLitifyCloud
  • 7 carried
  • 4 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Mitratech CaseCloud to Litify

Each row is a kind of record Mitratech CaseCloud 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 two kinds are confirmed in the analysis.

Records in Mitratech CaseCloud and their place in Litify
RecordIn Mitratech CaseCloudIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters, each with a stage, a status and its participants.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldAccounts and contacts in Salesforce, attached to matters by participant role.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldRelated Files on the matter, or an integrated document system.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmail can be sent from a matter. Filing from a mailbox needs the email integration.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 notesHeldMatter comments.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldMatter Calendar. CalendarRules is listed for court rules dates.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTask checklists and activity plans with dependencies.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTimekeepers, rates, UTBMS codes and batch time entry.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeld in partBillings are generated from time, expenses and fee arrangements.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 itselfHeldFields can be added to matters, participants and time layouts.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeldAdvoDoc templates, budget templates and activity plan templates.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntakes and intake forms with a convert-to-matter action.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 Mitratech CaseCloud.
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 Mitratech CaseCloud 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 Mitratech CaseCloud, 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 Mitratech CaseCloud 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 Mitratech CaseCloud is kept running until the checks on Litify are finished.

Where the data is now

CaseCloud data is Salesforce data, so leaving it starts with the org and not with an export button. What has to be established is which of the vendor’s applications the firm installed, how far the administrator customised them, and whether spend management records for outside counsel are in scope as well as the firm’s own matters.

  1. Three applications, one org

    Matter Management, Spend Management and Access Control are separate packages in the same org. A law firm may use only the first. A legal department may hold invoices from outside counsel in the second. Scope is set package by package, so nothing is extracted that the firm never used and nothing in use is missed.

  2. Access rules do not export

    Access Control decides which users and groups can see a matter and its related records. Those rules are configuration, not data, and the destination has its own security model. Restricted matters are listed with who may see them, and the equivalent restriction is rebuilt and tested in the new system before go-live.

  3. Intakes convert to matters

    An intake is its own record, filled in through an intake form and later converted to a matter. Converted intakes repeat what the matter already holds. Unconverted ones are leads or declined enquiries. The firm decides whether those go to the new system’s intake module, become contacts with a note, or stay behind.

  4. Fee arrangements drive the numbers

    Fees can be charged through a matter fee arrangement, once or on a recurring schedule, and the arrangement governs how time and expenses are treated. Few destinations model this the same way. Open arrangements are documented matter by matter, so that the next bill after the move is raised on the agreed terms.

  5. Legal holds and conflict checks

    The product keeps legal hold notices with their acknowledgements, and conflict checks can be run and their results managed. These are compliance records where the dates matter. If the destination has no place for them, they are exported as documents and filed to the matter or to the firm’s risk records.

More about moving off Mitratech CaseCloud

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

  1. Analysis

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

  4. Cutover

    Changes in Mitratech CaseCloud 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 Mitratech CaseCloud as at the cutover date. Mitratech CaseCloud 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 Mitratech CaseCloud 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 fromMitratech CaseCloud
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 Mitratech CaseCloud 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

Mitratech CaseCloud to Litify: what firms ask

We bought AdvoLogix years ago. Is this page about our system?

Almost certainly. The product was sold as AdvoLogix Matter Management before Mitratech introduced the CaseCloud name in late 2024, and the two share a help centre. A quick check is the Salesforce app launcher. If it shows matters and participants under an AdvoLogix or CaseCloud application, the firm is on this product whatever the invoice says.

Can we stay on Salesforce and only replace the legal application?

Yes, if the destination also runs on Salesforce, as Litify does. The accounts and contacts can stay where they are, and the matter records are remapped inside the org or moved to a new one. It is still a migration, because each product brings its own objects for matters, parties and time.

What about documents held in NetDocuments or iManage?

If the files are in a document system through the integration, they may not need to move at all. The matter in the new system is pointed at the existing workspace, provided the destination integrates with the same store. Where it does not, the files are moved and the matter number is used to file each one.

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

Most of it does on paper. Notes and trust ledgers 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 Mitratech CaseCloud 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 and trust ledgers 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

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

Moving from Mitratech CaseCloud 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.