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

Data migration route

Amicus Cloud to Litify migration

Amicus Cloud 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.

FromAmicus CloudCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Calendar: Carried across
  4. Tasks: Carried across
  5. Time and expenses: Carried across
  6. Emails: Carried with mapping
  7. Billing: Carried with mapping
  8. Documents: 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
  • 5 carried
  • 2 mapped
  • 7 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Amicus Cloud to Litify

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

Records in Amicus Cloud and their place in Litify
RecordIn Amicus CloudIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldThe vendor lists matter management as a core feature.Has 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 systemTo be confirmedHas a placeLoaded to the document component and attached to matters.Confirmed in the analysis
EmailsEmails saved to matters or to the storeHeld in partEmail is one of the main modules; how messages are tied to matters is not documented publicly.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 deadlinesHeldHas a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldTime and billing are built in, with client payments through the portal.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 payablesTo be confirmedTo 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 Amicus Cloud.
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 Amicus Cloud 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 Amicus Cloud, 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 Amicus Cloud 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 Amicus Cloud is kept running until the checks on Litify are finished.

Where the data is now

Little product documentation for Amicus Cloud is published today, so a move off it starts with looking at the firm’s own account, not a manual. What is actually there is listed in the analysis: matters, people, calendar entries, emails, time and bills. Anything beyond the modules the vendor named at launch, such as trust ledgers or stored documents, is confirmed from the live account before a destination is mapped.

  1. Not the desktop Amicus

    Three different things carry the Amicus name: this browser product, the Amicus Attorney desktop program, and Amicus Attorney running on a hosted desktop in Abacus Private Cloud. The browser product is not the desktop program under another name. The first step is confirming which one the firm signs in to, because a plan written for the desktop program does not fit this one.

  2. Email sits in the product

    Email is one of the modules on the Amicus Cloud dashboard, beside calendar and tasks. That raises a question a firm should settle early: which messages are attached to matters and need to travel with them, and which are simply the mailbox, which stays with the mail provider whatever happens to the practice system.

  3. Billing without a visible ledger

    Time entries and bills are inside Amicus Cloud. The public material does not say where the firm’s general ledger or trust records are kept. That is established in the analysis from the account and from the bookkeeper, since unpaid bills and any client money held must agree with the accounting records on the day of cutover.

  4. Portal and APX payments

    Clients may have been paying through the portal using APX. The card or bank details behind those payments belong to the payment service, not to the practice data, and do not move. Payment records against each bill can be carried. Clients on a recurring arrangement are identified so they can be set up again.

More about moving off Amicus Cloud

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

  1. Analysis

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

  4. Cutover

    Changes in Amicus Cloud 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 Amicus Cloud as at the cutover date. Amicus Cloud 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 Amicus Cloud 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 fromAmicus Cloud
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 Amicus Cloud 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

Amicus Cloud to Litify: what firms ask

Is Amicus Cloud the same thing as Amicus Attorney?

No. Amicus Attorney is a Windows program installed in the office or run on a hosted desktop. The Cloud product is separate, is used in a browser, and was called Amicus Online before 2020. A firm on one cannot assume that advice about the other applies to its data.

Is Amicus Cloud still being sold?

We cannot tell from public sources. CARET’s websites today present CARET Legal, AbacusLaw and Amicus Attorney, with no page for Amicus Cloud. A firm’s own agreement and account manager are the place to confirm its position. Either way, the planning for a move is the same.

What can we be sure will come across?

Before the analysis, only the obvious: matters, contacts, calendar entries, tasks, time and bills all have a place in any practice management system. For documents, trust records and anything the firm customised, the analysis shows what the account holds and where each item would sit in the destination.

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

Most of it does on paper. Documents, 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 Amicus Cloud data is loaded into Litify?

Emails and billing records are carried with mapping, so each mapping is agreed with you first. Documents, 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

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

Moving from Amicus Cloud 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.