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

Data migration route

Amicus Attorney to Clio Manage migration

Amicus Attorney is a server-based practice management system, and Clio Manage is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.

FromAmicus AttorneyServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Emails: Carried across
  5. Notes: Carried across
  6. Calendar: Carried across
  7. Tasks: Carried across
  8. Time and expenses: Carried with mapping
  9. Billing: Carried with mapping
  10. Trust money: Carried with mapping
  11. Custom fields: Carried with mapping
  12. Templates: Carried with mapping
ToClio ManageCloud
  1. Intake: Kept as a readable archive
Readable archiveNo place in Clio Manage
  • 7 carried
  • 5 mapped
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Amicus Attorney to Clio Manage

Each row is a kind of record Amicus Attorney holds, whether Clio Manage has a place for it, and what is planned. On this route seven kinds of record carry across, five kinds need mapping and one kind has no place in Clio Manage and is archived.

Records in Amicus Attorney and their place in Clio Manage
RecordIn Amicus AttorneyIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled Files; contacts and firm members each have a role on a File.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 systemHeldAttached to Files; Amicus-managed documents use check-in and check-out.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeHeldEmails saved to Files; calendars and contacts sync with Exchange.Has a placeHeld as communications on the matter, with phone logs.Carried across
NotesFile notes, matter notes and contact notesHeldHas a placeMatter notes and contact notes each have a template.Carried across
CalendarAppointments, court dates and deadlinesHeldCourt rule sets can be added for rules-based dates.Has 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 balancesHeld in partWith the Amicus Billing module; otherwise posted time goes to QuickBooks or PCLaw.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 balancesHeld in partTrust receipts, cheques and transfers come with Amicus Billing.Has a place in partA trust balance loads as one line per matter or contact; past transactions do not.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeldCustom fields, custom pages and Custom Records.Has a placeCreated first, then filled from the custom field templates.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates, plus Precedents that schedule a series of events.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partThe vendor lists lead management and intake; a File intake form is part of the product.No placeLeads and intake forms belong in Clio Grow.Kept as a readable archive

What the plans mean

Carried across
Clio Manage has a place for this kind of record. It is loaded there and checked against Amicus Attorney.
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.
Kept as a readable archive
Clio Manage has no place for it. It is exported in a format that opens without Amicus Attorney and handed to the firm as a read-only archive.

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 Attorney 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 Attorney’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.

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

Amicus keeps its records in SQL Server on the firm’s own server, so the structure can be read directly once that server is reachable. The work is in the things particular to it: Files with a role for every person, custom pages and Custom Records, documents it manages itself, and money that may sit in Amicus Billing, in QuickBooks or in PCLaw depending on what the firm licensed.

  1. Matters are called Files

    A File holds its people, events, notes, time and documents, and each person has a role on it. Firm members have roles too, such as senior litigator or paralegal. Those roles map to the matter staff and party fields of the new system, and the mapping is agreed before anything is loaded.

  2. Custom pages and Custom Records

    Firms add their own fields through custom pages and can define whole record types called Custom Records. Some destinations take custom fields but have nothing like a custom record. The analysis shows each one with how often it is filled, and the firm decides which become fields, which become notes and which stay behind.

  3. Where the money sits

    With Amicus Billing, bills, receipts, retainers and trust activity are inside the database. Without it, posted time goes to QuickBooks or PCLaw and the ledgers are there. Either way the accounting link holds a map between Files and the customer, job or matter on the other side, and that map is used to match the two.

  4. Two databases and a folder

    The vendor’s own server move guide backs up two SQL databases, Amicus and Amicus Media, and copies the Amicus Attorney Server folder. All three are needed for a complete picture. Documents attached by reference sit wherever the user saved them, so links that no longer resolve are reported before the trial load.

  5. Precedents schedule events

    A Precedent in Amicus is a set of tasks and deadlines, assigned by role, that is applied to a File. It is closer to a workflow than to a document template. The events it has already created come across as calendar entries and tasks, and the Precedent itself is rebuilt in the destination’s workflow tool.

More about moving off Amicus Attorney

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.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

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

  4. Cutover

    Changes in Amicus Attorney are frozen for an agreed window, the data is collected a final time and Clio Manage goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Amicus Attorney 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 Attorney 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 Attorney
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 Attorney 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 Attorney to Clio Manage: what firms ask

We are on an older Amicus version. Does that matter?

It changes where the data is. The Premium line runs on SQL Server, while the Small Firm Edition kept its data another way. Edition and version are confirmed at the start of the analysis, and the extraction is planned from that.

Do our time entries and unbilled work come across?

Posted and unposted time entries are both in the database with the File, firm member, activity code and rate. Unbilled time is loaded as unbilled so it can go on the next bill. Billed time is history: whether it loads as entries or stays in the read-only copy depends on the destination.

What happens to emails saved to Files?

Emails saved to a File are records in Amicus. They are filed to the same matter in the new system, as emails where it supports that and as documents where it does not. The Exchange link itself is not moved: mailboxes stay where they are in Microsoft 365 or on the firm’s mail server.

Do trust balances in Amicus Attorney have a place in Clio Manage?

In part. A trust balance loads as one line per matter or contact; past transactions do not. The analysis sets out which trust records have a place in Clio Manage and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

What happens to records Clio Manage has no place for?

On this route that is intake records. They are exported from Amicus Attorney in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Amicus Attorney data is loaded into Clio Manage?

Time entries, billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. 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 Attorney and Clio Manage are the names and marks of their owners, used here only to identify the two systems.

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