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

Data migration route

Keap to Centerbase migration

Keap 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.

FromKeapCloud
  1. Contacts: Carried across
  2. Documents: Carried across
  3. Notes: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Billing: Carried across
  7. Intake: Carried across
  8. Emails: Carried with mapping
  9. Custom fields: Carried with mapping
  10. Templates: Carried with mapping
ToCenterbaseCloud
  • 7 carried
  • 3 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Keap to Centerbase

Each row is a kind of record Keap 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.

Records in Keap and their place in Centerbase
RecordIn KeapIn CenterbaseWhat is planned
ContactsClients, other parties and referrersHeldContacts and companies, segmented by tags.Has a placeClients, related parties and prospects.Carried across
DocumentsFiles stored in or linked from the systemHeld in partFiles can be uploaded to a contact record.Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails sent from Keap, and one-to-one email synced with Gmail or Outlook.Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365.Carried with mapping
NotesFile notes, matter notes and contact notesHeldContact notes.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeld in partAppointments booked through the scheduler, synced with a Gmail or Outlook calendar.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
BillingInvoices, payments and debtor balancesHeld in partQuotes, one-off and recurring invoices, and card payments.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 itselfHeldCustom fields on contact and company records.Has a placeCreated and placed on page layouts before records are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partEmail templates and automation sequences.Has a place in partTemplates are rebuilt to merge Centerbase client and matter data.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldForms, landing pages, lead scoring and a sales pipeline.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 Keap.
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 Keap 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 Keap 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 Keap is kept running until the checks on Centerbase are finished.

Where the data is now

Keap’s contact list is the easy part: it exports to a spreadsheet with standard and custom fields. The harder parts are the tags, which are how the account is organised and which the contact export leaves out, and the automations, which exist only as running sequences. Invoices and recurring payments need their own plan if clients are being charged through it.

  1. Tags are not in the export

    Keap’s contact export covers standard and custom fields but not tags. The vendor’s suggested method is to run the Tag Tracker report and match it to the exported contact IDs. Since tags usually record what a contact enquired about, where they came from and what they have been sent, that matching step cannot be skipped.

  2. Automations stop at cutover

    A contact halfway through a follow-up sequence will stop receiving it when the account is switched off. The automation history shows who is in which sequence. Sequences worth keeping are rebuilt in the destination, and contacts are placed at the equivalent step so nobody gets the welcome email twice.

  3. Recurring payments

    Where clients pay a retainer or subscription through Keap, the card details sit with the payment processor, not in a spreadsheet the firm can export. Each recurring charge is listed with its amount and next date, and the firm arranges new payment authorities in the new billing system before the old ones are cancelled.

  4. Email marketability status

    Each contact’s email address carries a marketability status showing whether marketing email may be sent to it. That status is the consent record. It is exported with the contact and applied in the new mailing tool, so that people who opted out years ago stay opted out.

More about moving off Keap

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into Centerbase

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what Keap 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.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Keap, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Centerbase as a trial and checked against Keap: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Keap 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 Keap as at the cutover date. Keap 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 Keap 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 fromKeap
Moving toCenterbase

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 Keap 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.

  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 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

Keap to Centerbase: what firms ask

Is Keap the same as Infusionsoft?

Keap is the current name of the product and company that were called Infusionsoft, and some help pages still sit on the Infusionsoft domain. Thryv bought the company in 2024, and support articles now appear on Thryv’s site. For a move the name makes no difference: the account and its data are the same.

Can our contacts and their notes be exported together?

They come out as separate lists. Contacts export from the People view as a CSV, with larger exports sent as a download link by email. Notes and tags are reported on separately and joined back to each contact by its ID. The trial load checks that every note has landed on the right person.

Does billing history from Keap 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 Keap. 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 Keap have a place in Centerbase?

On paper, yes: each kind of record Keap 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 Keap 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.

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

Keap and Centerbase are the names and marks of their owners, used here only to identify the two systems.

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