Data migration route
SurePoint Finance Enterprise to Clio Manage migration
SurePoint Finance Enterprise and Clio Manage are each a cloud practice management system. Both run a whole practice, so this is a full move, and the financial records set the timetable.
SurePoint Finance EnterpriseCloud- Matters: Carried across
- Contacts: Carried across
- Calendar: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
Clio ManageCloud- Firm accounts: Kept as a readable archive
- Intake: Kept as a readable archive
- 3 carried
- 3 mapped
- 6 to confirm
- 2 archived
What moves
What moves from SurePoint Finance Enterprise to Clio Manage
Each row is a kind of record SurePoint Finance Enterprise holds, whether Clio Manage has a place for it, and what is planned. On this route three kinds of record carry across, three kinds need mapping, two kinds have no place in Clio Manage and are archived and six kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters, tracked from intake through billing and collections. | Has a placeImported from a matters template, after contacts. | Carried across |
| ContactsClients, other parties and referrers | HeldClient and matter contacts; marketing contacts may be in the separate SurePoint 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 system | To be confirmed | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeHeld as communications on the matter, with phone logs. | Confirmed in the analysis |
| 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 |
| CalendarAppointments, court dates and deadlines | HeldCalendars and dockets are part of the system. | Has a placeCalendar events have a migration template. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeTasks have a migration template. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | Held | 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 | HeldPaperless pre-bill edits, billing rules, LEDES e-billing and matter budgets. | 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 | Has a place in partA trust balance loads as one line per matter or contact; past transactions do not. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, accounts payable and cost recovery, for one or several entities. | 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 itself | To be confirmed | Has a placeCreated first, then filled from the custom field templates. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a placeRebuilt as Clio document templates with its merge fields. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partThe vendor describes matter intake; lead tracking sits in the separate CRM product. | 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 SurePoint Finance Enterprise.
- 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 SurePoint Finance Enterprise 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. SurePoint Finance Enterprise and Clio Manage each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with SurePoint Finance Enterprise’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of SurePoint Finance Enterprise 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 SurePoint Finance Enterprise is kept running until the checks on Clio Manage are finished.
Where the data is now
Leaving SurePoint Finance Enterprise
A firm on LMS may have been on it for a long time, and the system then holds its financial memory: bills, payments, cheques and journals going back years. Leaving means deciding how much of that memory travels and how the rest stays available. It also means replacing a general ledger and payables system, which makes the finance team the main party to the project.
Which SurePoint product
The SurePoint name covers several different systems: Finance Enterprise, which is LMS, Finance Core, which is Coyote, and the newer SurePoint Pro. Staff often just say SurePoint. The licence and the vendor’s support listing settle which one the firm runs, and that is confirmed before any method is chosen.
Decades of ledger history
LMS grew out of a specialist accounting package from Rippe & Kingston, and long-standing firms carry history from each stage. Old matter numbering schemes and timekeepers who left years ago are still referenced by live records. The analysis sets a cut-off year and shows what falls on each side of it.
Several entities, one system
Finance Enterprise supports multi-entity firms and multiple tax IDs within one system. A destination may need a separate set of books for each entity. The entity that owns each matter, bank account and vendor bill is established first, since intercompany balances have to agree on both sides at cutover.
Billing rules for each client
Built-in billing rules and e-billing support are used to stop invoices being rejected by corporate clients. Those rules were entered over years and are seldom written down anywhere else. They are extracted as a list for each client, and the first e-bills from the new system are checked against them.
Reports the partners rely on
With several hundred standard reports and custom dashboards, each firm has its own handful that drive compensation and management meetings. Reports do not migrate. The firm names the ones it cannot do without, and each is reproduced from the trial load and compared with the LMS original.
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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise, 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 SurePoint Finance Enterprise: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in SurePoint Finance Enterprise 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. SurePoint Finance Enterprise 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 SurePoint Finance Enterprise 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 SurePoint Finance Enterprise 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
SurePoint Finance Enterprise to Clio Manage: what firms ask
Is SurePoint LMS the same as SurePoint Finance Enterprise?
Yes. SurePoint’s own site labels Finance Enterprise as formerly LMS, and its support pages list it as SurePoint Finance Enterprise (LMS). It is a different system from Finance Core, which was Coyote Analytics, and from SurePoint Pro. A firm should confirm which one it holds before planning a move.
Where are our documents if we use LMS?
That varies by firm and we would not assume. The vendor describes pairing its practice and accounting products with separate document applications, so many firms keep documents in a dedicated document management system. Where each matter’s documents are held, and whether they need to move at all, is recorded in the analysis.
How much financial history should we take with us?
Enough to answer the questions the firm is really asked: open receivables with their invoices, trust ledgers, unbilled time, and usually a few years of billing by client and matter. Older detail stays in the read-only copy of LMS. The cut-off is agreed with the finance partner during the analysis.
Do trust balances in SurePoint Finance Enterprise 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 the firm’s accounts and intake records. They are exported from SurePoint Finance Enterprise 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 SurePoint Finance Enterprise data is loaded into Clio Manage?
Time entries, billing records and trust ledgers are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, tasks, custom fields and templates 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 SurePoint Finance Enterprise and into Clio Manage
Other destinations from SurePoint Finance Enterprise
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.
SurePoint Finance Enterprise and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from SurePoint Finance Enterprise 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.