Data migration route
HubSpot to Centerbase migration
HubSpot is a cloud CRM and intake system, and Centerbase is a cloud practice management system. Contacts and intake history move, and the matters themselves start life in Centerbase.
HubSpotCloud- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Billing: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
CenterbaseCloud- 7 carried
- 3 mapped
What moves
What moves from HubSpot to Centerbase
Each row is a kind of record HubSpot holds, whether Centerbase has a place for it, and what is planned. On this route seven kinds of record carry across and three kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldContacts and companies, linked by associations. | Has a placeClients, related parties and prospects. | 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 placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. | 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 place in partEmails saved to matters; mailboxes stay in Microsoft 365. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldNotes are logged as activities on a record. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partMeetings are logged as activities on records. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks have their own export. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | Held in partQuotes, invoices, payments and subscriptions exist as commerce records. | Has a placeThe vendor says billing history can be migrated; the depth is set in the analysis. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldCustom properties on every object, and custom objects. | Has a placeCreated and placed on page layouts before records are loaded. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partTemplates for marketing emails, pages and posts, not legal precedents. | Has a place in partTemplates are rebuilt to merge Centerbase client and matter data. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldForms, lead and deal pipelines, segments and marketing email. | Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis. | Carried across |
What the plans mean
- Carried across
- Centerbase has a place for this kind of record. It is loaded there and checked against HubSpot.
- Carried with mapping
- Centerbase 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
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 Centerbase 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 Centerbase 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 Centerbase 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 Centerbase 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 Centerbase
Centerbase takes practice, billing, trust and accounting data together, so loading a firm into it is a finance project as much as a matter load. Clients come first because matters inherit from them. The chart of accounts, bank accounts and accounting basis are fixed before balances go in. Because the product is configured per firm, the fields and layouts are designed before the trial load, not after.
Clients carry the billing rules
Billing arrangements, rates and accounting preferences are held on the client and passed to its matters. Source systems that create a fresh client for every matter leave duplicates behind. Those are merged during clean-up, so that each real client exists once and its terms are set in one place.
The ledger comes too
Centerbase has a full general ledger and runs on a cash or accrual basis. A firm arriving from a billing system with QuickBooks beside it is consolidating two sets of records. The accountant decides the basis and the opening date, and the trial balance loaded is agreed to the old books.
Trust and retainers are separate
A matter can hold multiple trust and retainer accounts. Source systems often blur the two, recording an advance on fees as trust or the reverse. Each balance is classified before loading, and client-level funds that were never tied to a matter are assigned to one or held at client level.
Decide the document home
Documents can go into built-in Document Storage, or stay in NetDocuments, iManage or SharePoint and be connected. Centerbase can create a standard folder structure when a matter is opened. That structure is agreed first, so migrated documents are filed into the same folders that new matters will get.
Fields are designed, not assumed
With unlimited custom fields, nearly every source field can have a home. That is a reason for restraint. Each one must be created and placed on a layout, and a page crowded with unused fields slows people down. The firm chooses which fields earn a place and which become a note.
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 Centerbase. 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 Centerbase 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 Centerbase 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 Centerbase. 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 Centerbase
Loaded data is not yet a working system. This is what NewLaw sets up in Centerbase, beyond the migration, so that people can work in it from the first day.
Setting up Centerbase is largely configuration. Bill templates, rate tables and the pre-bill approval chain have to match how the firm bills today, or the first billing cycle exposes the gaps. The chart of accounts and bank accounts are built with the finance team. Workflows that open matters, create folders and assign first tasks are written last, once the fields they depend on are settled.
Set-up decisions in Centerbase
- Bill templates and billing arrangements for each client type
- Rate tables, timekeepers and the pre-bill approval chain
- Chart of accounts, bank accounts and cash or accrual basis
- Custom fields, page layouts and automated workflows by practice
- Document storage choice and the standard matter folder structure
- Outlook and Microsoft 365 connection for email and calendar
Questions
HubSpot to Centerbase: 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 Centerbase?
Centerbase has a place for invoices and payments. The vendor says billing history can be migrated; the depth is set in the analysis. Open invoices and debtor balances are loaded and agreed to the aged debtors report from HubSpot. How many years of paid invoices come across as records is the firm’s choice, and older ones are often kept as PDF copies.
Does everything in HubSpot have a place in Centerbase?
On paper, yes: each kind of record HubSpot holds has a place in Centerbase. 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 HubSpot data is loaded into Centerbase?
Emails, 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 Centerbase
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 Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from HubSpot to Centerbase?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.