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

Data migration route

Clio Manage data to Microsoft SQL Server

Clio Manage is a cloud practice management system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Clio Manage holds and keeps it readable and open to queries.

FromClio ManageCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Notes: Exported in full
  4. Calendar: Exported in full
  5. Tasks: Exported in full
  6. Time and expenses: Exported in full
  7. Billing: Exported in full
  8. Trust money: Exported in full
  9. Firm accounts: Exported in full
  10. Intake: Exported in full
  11. Documents: Exported with mapping
  12. Emails: Exported with mapping
  13. Custom fields: Exported with mapping
  14. Templates: Exported with mapping
ToMicrosoft SQL ServerServer
  • 10 carried
  • 4 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Clio Manage to Microsoft SQL Server

Each row is a kind of record Clio Manage holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route ten kinds of record carry across and four kinds need mapping.

Records in Clio Manage and their place in Microsoft SQL Server
RecordIn Clio ManageIn Microsoft SQL ServerWhat 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 placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldPerson and company contacts; related contacts link other parties to a matter.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldStored under contacts and matters in folders, with version history.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
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 place in partAs message files with an index table, or as rows of header fields.Exported with mapping
NotesFile notes, matter notes and contact notesHeldMatter notes and contact notes.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldHas a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTime entries and expense entries are both called activities.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldBills move from draft through approval to unpaid and paid.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldTrust funds can be held at client level or matter level.Has a placeTransactions and balances for look-up; it is not a trust accounting system.Exported in full
Firm accountsGeneral ledger, office account and payablesHeld in partClio Accounting is a separate Clio product, documented for the US and Canada.Has a placeGeneral ledger journals and balances, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfHeldMatter and contact custom fields, shared with Clio Grow.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates with merge fields, made from Word, Excel, PowerPoint and PDF files.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLead pipeline and intake forms are in Clio Grow, a companion product.Has a placeEnquiry rows, where the source recorded them.Exported in full

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Clio Manage.
Exported with mapping
Microsoft SQL Server holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.

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

Not a new system. A complete copy the firm can query.

Writing Clio Manage out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Clio Manage as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Clio Manage is hosted by its maker and Microsoft SQL Server sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Clio Manage will release depends on its export tools, and that is confirmed in the analysis.

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

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Clio Manage holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Clio Manage holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Microsoft SQL Server as a trial and checked against Clio Manage: record counts, totals where Clio Manage holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Clio Manage, the export is run a final time and checked again. There is nothing to go live. Clio Manage is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toMicrosoft SQL Server

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 Microsoft SQL Server. 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

Structure, permissions and handover

Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

Clio Manage to Microsoft SQL Server: 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.

Does the copy in Microsoft SQL Server hold trust ledgers from Clio Manage?

Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Clio Manage as at the export date.

Does everything in Clio Manage have a place in Microsoft SQL Server?

On paper, yes: each kind of record Clio Manage holds has a place in Microsoft SQL Server. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before Clio Manage is written out to Microsoft SQL Server?

Documents, emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.

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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from Clio Manage to Microsoft SQL Server?

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

We reply within one business day.