Data migration route
HubSpot to Clio Manage migration
HubSpot is a cloud CRM and intake system, and Clio Manage is a cloud practice management system. Contacts and intake history move, and the matters themselves start life in Clio Manage.
HubSpotCloud- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
Clio ManageCloud- Intake: Kept as a readable archive
- 6 carried
- 3 mapped
- 1 archived
What moves
What moves from HubSpot to Clio Manage
Each row is a kind of record HubSpot holds, whether Clio Manage has a place for it, and what is planned. On this route six kinds of record carry across, three kinds need mapping and one kind has no place in Clio Manage and is archived.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldContacts and companies, linked by associations. | 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 | Held in partA files tool holds uploaded files. There are no matter folders. | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails logged to the CRM appear as activities on the record timeline. | Has a placeHeld as communications on the matter, with phone logs. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldNotes are logged as activities on a record. | Has a placeMatter notes and contact notes each have a template. | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partMeetings are logged as activities on records. | Has a placeCalendar events have a migration template. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks have their own export. | Has a placeTasks have a migration template. | Carried across |
| BillingInvoices, payments and debtor balances | Held in partQuotes, invoices, payments and subscriptions exist as commerce records. | Has a place in partAn outstanding balance loads as one line per matter; past invoices do not. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | HeldCustom properties on every object, and custom objects. | Has a placeCreated first, then filled from the custom field templates. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partTemplates for marketing emails, pages and posts, not legal precedents. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldForms, lead and deal pipelines, segments and marketing email. | 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 HubSpot.
- 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.
- Kept as a readable archive
- Clio Manage has no place for it. It is exported in a format that opens without HubSpot 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
Contacts and enquiries move. Matters begin in the new system.
A CRM knows people: who enquired, who referred them, what was sent and when. It does not know matters the way a practice system does. So the move from HubSpot to Clio Manage is mostly a contacts job, and contacts are where duplicates live. The same person appears as a lead, a client and a referrer, sometimes under three email addresses. They are merged before extraction where they can be identified, because Clio Manage will invoice and receipt against these records.
Pipelines, campaigns and automations seldom have a direct equivalent in a practice system. Open enquiries can be loaded as contacts with a note of their stage, or opened as matters if the firm wants them worked from the first day. Intake forms and email sequences are set up again in whatever Clio Manage or its intake tool provides. Past correspondence is kept as notes or documents on the contact, so the history of a relationship can still be read.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of HubSpot 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 HubSpot is kept running until the checks on Clio Manage are finished.
Where the data is now
Leaving HubSpot
HubSpot exports each object as its own spreadsheet: contacts, companies, deals and so on, with their properties and associations. The activity on those records, meaning the calls, notes and emails, is not in those files and has to be collected separately. A move is therefore two jobs: the records, and the history that hangs off them.
Activities are a separate export
A record export downloads current property values and associations. HubSpot’s own guidance is that contact activities such as calls and notes come from exporting individual contacts, from certain activity reports, or from the engagements API. Which of those routes suits a full history across thousands of contacts is settled in the analysis, and each timeline that is carried arrives as dated notes.
Unsubscribes come with the contacts
Exporting all contacts includes the people who have unsubscribed from all email. That is the firm’s record of who must not be emailed, and it has to survive the move. The unsubscribed flag is carried into whichever tool will send the firm’s mail next, before anything is sent from it.
Deals standing in for matters
Some law firms on HubSpot record each new enquiry as a deal and close it as won when the client signs. A won deal is roughly a matter opening, and a lost one is a declined enquiry. Deal stages are mapped to the destination’s intake statuses, and won deals are checked against existing matters so no client is created twice.
Hundreds of properties, few used
A HubSpot account gathers properties from every integration and form ever connected to it. Exporting all properties on records gives one column for each. The property list is exported first and checked for how many records hold a value in each, and only the fields the firm recognises are mapped.
The website may live there
Forms, landing pages and sometimes the whole website are built in HubSpot. If the firm is closing the account and not just moving its CRM data, pages, posts and files are exported as well, and the enquiry forms are rebuilt to feed the new system. HubSpot’s export guide lists each of these separately.
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.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what HubSpot 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 HubSpot, 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 HubSpot: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in HubSpot 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 HubSpot as at the cutover date. HubSpot 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 HubSpot 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 HubSpot 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
HubSpot to Clio Manage: what firms ask
Can we keep HubSpot for marketing and move only the client records?
Yes. Clients and matters go to the practice system, and HubSpot keeps sending newsletters and capturing enquiries. What matters then is the hand-over point: which system creates the contact first, and how a signed client passes from a deal to a matter without being keyed in twice.
Does the email history on each contact come across?
Emails logged to HubSpot’s timeline are activities, which sit outside the standard record export. HubSpot’s guidance names its API as one way to retrieve them, and once retrieved they can be loaded as correspondence notes against the client or matter. Emails that were never logged to HubSpot are still in the lawyers’ mailboxes and are outside this move.
Does billing history from HubSpot move into Clio Manage?
In part. An outstanding balance loads as one line per matter; past invoices do not. Open items are matched to what Clio Manage can hold, and the rest of the billing history is kept as reports that open without HubSpot.
What happens to records Clio Manage has no place for?
On this route that is intake records. They are exported from HubSpot 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 HubSpot data is loaded into Clio Manage?
Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from HubSpot and 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.
HubSpot and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from HubSpot 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.