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

Data migration route

TimeSolv to Clio Manage migration

TimeSolv is a cloud 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.

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

What moves

What moves from TimeSolv to Clio Manage

Each row is a kind of record TimeSolv 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, one kind has no place in Clio Manage and is archived and three kinds are confirmed in the analysis.

Records in TimeSolv and their place in Clio Manage
RecordIn TimeSolvIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters sit under clients. They carry billing settings more than case detail.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldClients and their contacts; leads are tracked in the CRM.Has a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemHeldNested folders and tags inside TimeSolv, or a linked Dropbox or NetDocuments account.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 notesHeldNotes on clients and matters.Has a placeMatter notes and contact notes each have a template.Carried across
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events have a migration template.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeldProject management with phases, tasks, estimates and budgets.Has a placeTasks have a migration template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldThe core record, entered on the web, on mobile or offline through the TimeSync 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 balancesHeldTrust balances can be applied to approved invoices.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 itselfTo be confirmedHas a placeCreated first, then filled from the custom field templates.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partDocuments can be generated from client and matter data.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldCRM tracks prospects through intake statuses the firm defines.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 TimeSolv.
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 TimeSolv 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 TimeSolv 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 TimeSolv. 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 TimeSolv as at the cutover date, and that load is rehearsed before it is done for real.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of TimeSolv 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 TimeSolv is kept running until the checks on Clio Manage are finished.

Where the data is now

When the destination is a full practice management system, leaving TimeSolv is only part of the job. TimeSolv knows who the client is, what was billed and what is owed. It does not know the court, the other side or the next deadline. Its billing records move across, and the rest of each matter has to be gathered from wherever the firm has been keeping it.

  1. A matter is a billing file

    A TimeSolv matter holds rates, billing arrangements, budgets and balances. The parties, key dates and file notes that a practice management system expects are often in Outlook, a spreadsheet or the paper file. Part of the analysis is asking where those live, and whether they are loaded with the billing data or entered as matters are next worked on.

  2. Trust here, ledger elsewhere

    Client trust balances are kept in TimeSolv, while the bank accounts and general ledger are in QuickBooks, Xero or AccountEdge. The trust listing from TimeSolv and the trust bank balance from the accounting package are agreed with each other before cutover. Only then are opening balances entered in the new system.

  3. Phases, tasks and budgets

    Matter plans split a job into phases and tasks with estimated hours and fixed fees, and time is recorded against task codes. Many destinations bill by matter with no phase beneath it. Where budgets matter to clients, the firm decides whether phases become sub-matters, activity codes or a report run from the old data.

  4. Documents in three places

    Files may be in TimeSolv’s own folders, in a linked Dropbox account or in NetDocuments workspaces. A single firm can have all three if it changed approach over the years. Each store is listed with its volume, and documents already in NetDocuments or Dropbox can often stay where they are.

  5. Many years of time entries

    The product dates from 1999, so a long-standing firm can hold a very long run of billed time in it. Loading all of it into a new system is seldom worth the effort. A common split is open matters with full detail, closed matters as a summary, and the complete history kept in the read-only copy.

More about moving off TimeSolv

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

  4. Cutover

    Changes in TimeSolv 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. TimeSolv 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 TimeSolv 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 fromTimeSolv
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 TimeSolv 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

TimeSolv to Clio Manage: what firms ask

We use TimeSolv with QuickBooks. Which one is the source for debtor balances?

TimeSolv, because that is where invoices are raised and payments applied by matter. QuickBooks holds the same totals at firm level once synced. The two are compared in the analysis. A difference usually points to a payment entered on one side only, and it is fixed before the trial load.

Will our unbilled time come across?

Unbilled time and expenses are the records most worth moving, since they are money not yet invoiced. They are loaded against the right matter and timekeeper with their original dates and narratives. Running a final billing cycle in TimeSolv first leaves less work in progress to carry.

We are on the Pro edition, not Legal. Is the move any different?

The records are the same kind: clients, the jobs under them, time, expenses and invoices. Extraction and checking are planned the same way. What changes is the destination, since a system built for law firms will expect matter types and trust rules that a consultancy or accounting practice never needed.

Do trust balances in TimeSolv 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 TimeSolv 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 TimeSolv data is loaded into Clio Manage?

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

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

Moving from TimeSolv 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.