Data migration route
Sage Timeslips to Clio Manage migration
Sage Timeslips is a desktop 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.
Sage TimeslipsDesktop- Matters: Carried across
- Contacts: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
Clio ManageCloud- 2 carried
- 5 mapped
- 1 to confirm
What moves
What moves from Sage Timeslips to Clio Manage
Each row is a kind of record Sage Timeslips holds, whether Clio Manage has a place for it, and what is planned. On this route two kinds of record carry across, five kinds need mapping and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partBills by client; many firms enter each matter as its own client. | Has a placeImported from a matters template, after contacts. | Carried across |
| ContactsClients, other parties and referrers | Held in partClients and their contacts. | Has a placePeople and companies, with related contacts linked to matters by a separate template. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeMatter notes and contact notes each have a template. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expense entries, called slips. | 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 balances | HeldBills the firm designs itself, payments and receivable balances. | 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 balances | Held in partClient funds accounts track money held for clients. | 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 itself | Held | Has a placeCreated first, then filled from the custom field templates. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partBill layouts designed in the product. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
What the plans mean
- Carried across
- Clio Manage has a place for this kind of record. It is loaded there and checked against Sage Timeslips.
- 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.
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 Sage Timeslips 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 Sage Timeslips. 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 Sage Timeslips as at the cutover date, and that load is rehearsed before it is done for real.
Sage Timeslips 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
Leaving Sage Timeslips
Timeslips does one job, so a move off it is about time, bills and balances, with matters and contacts built from what the billing records imply. The main decision is how the firm used the client list. Some entered one client per matter, others one per person. That convention is read from the data before any mapping is done.
A client may be a matter
The program bills clients, and firms that needed matters adapted the client list to carry them. A common pattern is one Timeslips client per matter, with the two nickname fields holding the client name and the matter. The move turns that into clients with matters beneath, which means deciding which entries are the same person.
Slips are the history
Each piece of time and each expense is a slip with a date, timekeeper, activity, rate and billing status. Unbilled slips become unbilled time and disbursements in the destination. Billed slips are history, loaded where the new system accepts billed entries and otherwise left in a read-only copy with the invoices.
Client funds and trust
Money held for a client is tracked in client funds accounts inside Timeslips. A firm that holds trust money may also keep a formal trust ledger and bank reconciliation in an accounting program. Both are looked at, and the balance loaded as trust is the one that agrees to the bank.
Firebird behind the program
Timeslips Premium stores its data in a Firebird database, either on one PC or on a database server for network installs. On a network the database components sit on the server and the program in a shared folder. A backup made from inside Timeslips gives a copy to work from without disturbing the live database.
The books are in another product
Receivables are kept in Timeslips, but the firm’s general ledger sits in a separate accounting package. The receivable balance in Timeslips and the debtors figure in that package should agree before cutover. Where they have drifted apart, the firm decides which is right before either is loaded.
Where it is going
Arriving in Clio Manage
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what Sage Timeslips 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.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Sage Timeslips, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Clio Manage as a trial and checked against Sage Timeslips: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Sage Timeslips 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. Sage Timeslips 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 Sage Timeslips 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Sage Timeslips 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.
- 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
Sage Timeslips to Clio Manage: what firms ask
Can we split our client list into clients and matters?
Yes, and it is usually the main clean-up task. The analysis groups Timeslips clients that look like the same person or company and proposes a client with matters beneath. Someone at the firm then reviews the list, because only a person who knows the files can say whether two similar names are one client.
Do our bill layouts carry over?
No. Layouts designed in Timeslips belong to it. The firm chooses the formats it still sends, and each is rebuilt as an invoice template in the new system. Clients who receive LEDES files are tested separately with a real invoice before the first live bill run.
What happens to our custom fields?
Custom fields are listed with how often they are filled, and the ones that matter are mapped to fields on the client or matter in the new system. A field that only ever held a matter number or a file reference usually becomes the matter number itself.
Do trust balances in Sage Timeslips 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.
Does everything in Sage Timeslips have a place in Clio Manage?
Most of it does on paper. Notes 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 Clio Manage is kept as a readable archive, and you see which before the move.
What has to be decided before Sage Timeslips 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. Notes are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Sage Timeslips and into Clio Manage
Other destinations from Sage Timeslips
Other systems that move into Clio Manage
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Sage Timeslips and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from Sage Timeslips 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.