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

Data migration route

Amicus Cloud to Clio Manage migration

Amicus Cloud and Clio Manage are each a cloud practice management system. Both run a whole practice, so this is a full move, and the financial records set the timetable.

FromAmicus CloudCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Emails: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Time and expenses: 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
ToClio ManageCloud
  • 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 Clio Manage

Each row is a kind of record Amicus Cloud holds, whether Clio Manage 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 Clio Manage
RecordIn Amicus CloudIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldThe vendor lists matter management as a core feature.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldHas a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeFiled under the matter; Clio scopes document migration separately from data.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 placeHeld as communications on the matter, with phone logs.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeMatter notes and contact notes each have a template.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldHas a placeCalendar events have a migration template.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeTasks have a migration template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldHas a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Carried with mapping
BillingInvoices, payments and debtor balancesHeldTime and billing are built in, with client payments through the portal.Has a place in partAn outstanding balance loads as one line per matter; past invoices do not.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partA trust balance loads as one line per matter or contact; past transactions do not.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCreated first, then filled from the custom field templates.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a placeRebuilt as Clio document templates with its merge fields.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeLeads and intake forms belong in Clio Grow.Confirmed in the analysis

What the plans mean

Carried across
Clio Manage has a place for this kind of record. It is loaded there and checked against Amicus Cloud.
Carried with mapping
Clio Manage 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

The whole practice moves, accounts included.

A move between two practice management systems is the widest kind there is. Amicus Cloud and Clio Manage each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.

The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with Amicus Cloud’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.

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 Clio Manage 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

Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.

  1. Matters link by client name

    The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.

  2. Decide the numbering scheme first

    Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.

  3. Balances, one line each

    Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.

  4. Custom fields must exist

    Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.

  5. Rates and permissions by hand

    Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.

More about moving into Clio Manage

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  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 Clio Manage. 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 Clio Manage 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 Clio Manage 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 toClio Manage

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 Clio Manage. 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 Clio Manage

Loaded data is not yet a working system. This is what NewLaw sets up in Clio Manage, beyond the migration, so that people can work in it from the first day.

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Questions

Amicus Cloud to Clio Manage: 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 Clio Manage?

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 Clio Manage 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 Clio Manage?

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 Clio Manage 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 Clio Manage?

Time entries 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 Clio Manage are the names and marks of their owners, used here only to identify the two systems.

Moving from Amicus Cloud to Clio Manage?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.