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

Data migration route

Clio Manage to SmartAdvocate migration

Clio Manage is a cloud practice management system, and SmartAdvocate is a cloud case management system for personal injury work. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

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

What moves

What moves from Clio Manage to SmartAdvocate

Each row is a kind of record Clio Manage holds, whether SmartAdvocate has a place for it, and what is planned. On this route nine kinds of record carry across, three kinds need mapping and two kinds are confirmed in the analysis.

Records in Clio Manage and their place in SmartAdvocate
RecordIn Clio ManageIn SmartAdvocateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldOpen, Pending or Closed, with a display number built from a firm-wide numbering scheme.Has a placeCases by case type, with master and member relationships.Carried across
ContactsClients, other parties and referrersHeldPerson and company contacts; related contacts link other parties to a matter.Has a placeCarried across
DocumentsFiles stored in or linked from the systemHeldStored under contacts and matters in folders, with version history.Has a placeDocuments page, by category and subcategory.Carried across
EmailsEmails saved to matters or to the storeHeldFiled from Outlook as email logs, or forwarded to a matter and stored as EML files.Has a placeEmails are attached to cases.Carried across
NotesFile notes, matter notes and contact notesHeldMatter notes and contact notes.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldHas a placeAppointments and critical deadlines.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime entries and expense entries are both called activities.Has a placeTracked time entries.Carried across
BillingInvoices, payments and debtor balancesHeldBills move from draft through approval to unpaid and paid.Has a place in partInvoices for hourly matters. Past invoices are scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust funds can be held at client level or matter level.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partClio Accounting is a separate Clio product, documented for the US and Canada.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldMatter and contact custom fields, shared with Clio Grow.Has a place in partConfirmed in the analysis for each field with no standard home.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates with merge fields, made from Word, Excel, PowerPoint and PDF files.Has a place in partTemplates are rebuilt with SmartAdvocate merge codes.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLead pipeline and intake forms are in Clio Grow, a companion product.Has a placeIntake and lead records.Carried across

What the plans mean

Carried across
SmartAdvocate has a place for this kind of record. It is loaded there and checked against Clio Manage.
Carried with mapping
SmartAdvocate 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 SmartAdvocate. 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 Clio Manage has to be given a case type in SmartAdvocate, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in SmartAdvocate is exported as reports and ledgers the firm can open without Clio Manage, 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 Clio Manage 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 Clio Manage is kept running until the checks on SmartAdvocate are finished.

Where the data is now

Leaving Clio Manage is mostly a question of what comes out and in what form. Clio’s export page produces spreadsheets of contacts, matters, notes, tasks, calendar entries and time, and balances come from reports. Documents and billing history are not in those spreadsheets, so they are collected separately and joined back to the right matters.

  1. The display number can change

    A matter’s display number is built from a firm-wide scheme: matter number, client name, year and other parts in a chosen order. An administrator can change the scheme and apply it to every existing matter. The number in the export may therefore differ from the one on older letters. We check the Client Reference field as well.

  2. Trust held at client level

    Clio lets a firm hold trust funds against the client as a whole, not only against a matter. Many trust ledgers elsewhere are strictly per matter. Each client-level balance then has to be allocated to a matter before cutover, and the accounts team makes that allocation in Clio so the closing report already shows it.

  3. Activities and communications

    Time entries and expense entries are both called activities and export as separate lists. Filed emails and phone logs are communications. An email forwarded to a matter’s Maildrop address is stored as an EML file, while one filed from Outlook is an email log. The analysis counts each kind, since they land in different places.

  4. Documents may sit outside Clio

    Files can be stored in Clio itself or in a connected service. With the OneDrive for Business integration, for example, Clio creates a root folder with a subfolder for every client and matter. Before planning the document move we establish which store each office has been saving to, and whether both hold files.

  5. Draft bills at cutover

    A bill in Clio is a draft, pending approval, unpaid or paid, and a draft does not yet count towards the client’s balance. Before the final collection the accounts team approves or discards every draft. The debtor figure taken across is then the one on Clio’s accounts receivable report, with no half-finished bills behind it.

More about moving off Clio Manage

Where it is going

SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.

  1. Map to fields, not notes

    The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.

  2. Case types and statuses

    Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.

  3. Document categories

    Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.

  4. Working with the vendor’s conversion

    SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.

  5. Choosing Server or Cloud

    The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.

More about moving into SmartAdvocate

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 SmartAdvocate 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 Clio Manage and checking each trial against Clio Manage.

  1. Analysis

    We read what Clio Manage holds and how its records link, then agree with you, field by field, where each piece will sit in SmartAdvocate. 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 Clio Manage, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into SmartAdvocate as a trial and checked against Clio Manage: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Clio Manage are frozen for an agreed window, the data is collected a final time and SmartAdvocate 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 Clio Manage as at the cutover date. Clio Manage 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 Clio Manage 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 fromClio Manage
Moving toSmartAdvocate

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

    What is in it, how its records link, and where each piece would sit in SmartAdvocate. 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 SmartAdvocate

Loaded data is not yet a working system. The maker of SmartAdvocate runs or arranges the set-up of its product, so this is what has to be decided and put in place in SmartAdvocate, whoever does the work, before people rely on it from the first day.

Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.

Set-up decisions in SmartAdvocate

  • Choose the Server or Cloud edition with IT
  • Define case types, statuses and staff roles
  • Build WorkPlans and Automated Procedures for each case type
  • Convert letters and forms into templates with merge codes
  • Install the Outlook plugin and agree email filing habits
  • Set up intake screens, lead sources and dashboards

Questions

Clio Manage to SmartAdvocate: what firms ask

Can our matter numbers stay the same when we leave Clio?

The destination decides. If it accepts a supplied matter number, the Clio display number is loaded as it stands. Because Clio’s scheme can include the client’s name, some firms take the chance to shorten it. Where the new system insists on its own numbering, the Clio number is kept in a reference field.

Does our billing history come out of Clio?

Time and expense entries export as lists, and outstanding balances come from the accounts receivable report. Whether the new system can hold past invoices as invoices depends on that system. Where it cannot, we agree with the firm how the history is kept: as PDF copies on each matter, or in the archived Clio data.

We also use Clio Grow. Is that a separate job?

It is a separate product with its own data, so it is scoped separately. Matters already converted from Grow exist in Clio Manage and move with it. What remains in Grow is the pipeline: leads not yet hired, intake forms and signed engagement documents. The analysis shows how much of that the firm still needs.

Do trust balances in Clio Manage have a place in SmartAdvocate?

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 Clio Manage before the plan is fixed. If SmartAdvocate 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 Clio Manage have a place in SmartAdvocate?

Most of it does on paper. 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 SmartAdvocate is kept as a readable archive, and you see which before the move.

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

Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. 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

Clio Manage and SmartAdvocate are the names and marks of their owners, used here only to identify the two systems.

Moving from Clio Manage to SmartAdvocate?

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

We reply within one business day.