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

Data migration route

Coyote Analytics to Clio Manage migration

Coyote Analytics is a server-based accounting and billing system, and Clio Manage is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Clio Manage are built around them.

FromCoyote AnalyticsServer
  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 with mapping
  7. Billing: Carried with mapping
  8. Custom fields: Carried with mapping
  9. Templates: Carried with mapping
  10. Emails: Confirmed in the analysis
  11. Notes: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
ToClio ManageCloud
  1. Firm accounts: Kept as a readable archive
  2. Intake: Kept as a readable archive
Readable archiveNo place in Clio Manage
  • 5 carried
  • 4 mapped
  • 3 to confirm
  • 2 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Coyote Analytics to Clio Manage

Each row is a kind of record Coyote Analytics holds, whether Clio Manage has a place for it, and what is planned. On this route five kinds of record carry across, four kinds need mapping, two kinds have no place in Clio Manage and are archived and three kinds are confirmed in the analysis.

Records in Coyote Analytics and their place in Clio Manage
RecordIn Coyote AnalyticsIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldIncludes referral tracking and conflict searches.Has a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemHeldDocument numbering, indexing, OCR search and custom folder structures.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld as communications on the matter, with phone logs.Confirmed in the analysis
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 deadlinesHeldSynchronises with Microsoft Exchange; calendar rules integration.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 unbilledHeldTime and expense entry, including a mobile app.Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Carried with mapping
BillingInvoices, payments and debtor balancesHeldHas 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 payablesHeldGeneral ledger, accounts payable, budgeting and bank reconciliation.No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partCustom fields on contacts.Has a placeCreated first, then filled from the custom field templates.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partDocument and email generation.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldClient intake and conflict approval workflows.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 Coyote Analytics.
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.
Kept as a readable archive
Clio Manage has no place for it. It is exported in a format that opens without Coyote Analytics 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

Time, bills and balances move. How much history is a decision.

Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in Coyote Analytics needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.

How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of Coyote Analytics. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Clio Manage are agreed to the trial balance and aged debtors from Coyote Analytics as at the cutover date, and that load is rehearsed before it is done for real.

Coyote Analytics 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

A firm leaving Coyote is moving its accounting system, and often its conflicts database and document index as well. The financial data is the centre: unbilled time and costs, invoices and receipts, the general ledger and payables. Which of the practice modules were really used varies firm to firm, so the analysis starts by finding out which ones hold live records.

  1. Find the live modules

    Coyote was sold as modules, and a firm may have run the financial side with another product for documents and calendars. A module holding a few hundred old records is treated differently from one in daily use. Record counts and last-used dates for each module are the first thing reported back.

  2. Budgets at three levels

    Budgets can be kept on the general ledger, on timekeepers and on individual client matters, with alerts. A matter budget is often something the client was promised. Budgets are extracted with the matter, and loaded where the destination has a budget field or carried as a note where it does not.

  3. Allocations and profitability

    Profitability reports for timekeepers and practice areas depend on direct and indirect allocation rules set up in Coyote. Loading the transactions elsewhere does not bring the rules with them. The rules are written down during the analysis so the same view can be rebuilt in the new reporting tool.

  4. Records and containers

    Records management tracks physical containers, the documents in them and where each is stored. That is the firm’s index to its boxes. Few practice systems have a place for it. It usually comes across as a field or note on the closed matter, or as a register the records clerk keeps.

  5. Hosted or on your server

    Firms on the original version hold the database on their own server. Those on Coyote Analytics Cloud have it hosted by the vendor on Amazon Web Services and reach it through a browser. How a copy of the data is obtained differs between the two, and is arranged at the start.

More about moving off Coyote Analytics

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

  4. Cutover

    Changes in Coyote Analytics 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 Coyote Analytics as at the cutover date. Coyote Analytics 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 Coyote Analytics 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 fromCoyote Analytics
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 Coyote Analytics 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

Coyote Analytics to Clio Manage: what firms ask

Is Coyote Analytics now SurePoint Finance Core?

SurePoint bought Coyote Analytics in June 2022 and said it would stay a standalone product. The old Coyote web address now leads to SurePoint’s Finance Core page, where customers quoted still call it Coyote. Your contract and login screen show which name applies to you. The data is the same under both.

Do we keep our client and matter numbers?

Client and matter numbers are carried exactly where the destination lets the firm set them. Where it generates its own, the Coyote number goes into a reference field that staff can search. Accounts staff tend to know matters by number, so this is settled early.

Can our client billing rules move?

The invoices already sent do not need to. What moves is the set-up behind them: task and activity codes, timekeeper classifications, client billing rules and rates. These are extracted as lists and rebuilt in the destination, then tested with one real client before the first live bill run.

Do trust balances in Coyote Analytics 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 Coyote Analytics 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.

What happens to records Clio Manage has no place for?

On this route that is the firm’s accounts and intake records. They are exported from Coyote Analytics 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 Coyote Analytics data is loaded into Clio Manage?

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

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

Moving from Coyote Analytics 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.