Data migration route
Harvest to Centerbase migration
Harvest is a cloud accounting and billing system, and Centerbase is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Centerbase are built around them.
HarvestCloud- Matters: Carried across
- Contacts: Carried across
- Notes: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Documents: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
CenterbaseCloud- 6 carried
- 3 to confirm
What moves
What moves from Harvest to Centerbase
Each row is a kind of record Harvest holds, whether Centerbase has a place for it, and what is planned. On this route six kinds of record carry across and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partProjects under clients stand in for matters; there are three project types. | Has a placeLoaded under their client, with practice-specific custom fields. | Carried across |
| ContactsClients, other parties and referrers | Held in partClients and client contacts, kept mainly as invoice recipients. | Has a placeClients, related parties and prospects. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partFree-text notes on each time entry. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partTasks are categories of work for time entries, not to-dos. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimers and timesheets by person, project and task, with approvals. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldInvoices and estimates, with online payment through Stripe or PayPal. | 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 | To be confirmed | Has a placeCreated and placed on page layouts before records are loaded. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt to merge Centerbase client and matter data. | Confirmed in the analysis |
What the plans mean
- Carried across
- Centerbase has a place for this kind of record. It is loaded there and checked against Harvest.
- 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 Harvest 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 Harvest. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Centerbase are agreed to the trial balance and aged debtors from Harvest as at the cutover date, and that load is rehearsed before it is done for real.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Harvest 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 Harvest is kept running until the checks on Centerbase are finished.
Where the data is now
Leaving Harvest
Harvest knows about clients, projects, tasks, people, time entries, expenses, invoices and estimates. It does not know about matters or trust money. A firm leaving it for a practice system is turning projects into matters and carrying across time and invoice history, while the firm’s books stay in the accounting package Harvest was feeding.
Client, then project
A Harvest client record holds a name, an address and a currency, with contacts added mainly so invoices reach the right person. The detail a legal system wants about a client, such as other parties or a responsible lawyer, was never recorded here and is gathered from elsewhere or added after loading.
Tasks are not to-dos
In Harvest a task is a category of work, such as drafting or attendance, that a time entry is logged against, and it can carry its own billable rate. Tasks map to activity codes in a practice system. They are not a list of things waiting to be done on a matter.
Three ways to set rates
A Time & Materials project bills at a project rate, a rate per person or a rate per task. The same lawyer can therefore have different rates on different projects. Historical time is loaded with the rate it was recorded at, and the going-forward rate table is built separately in the new system.
Invoices copied to the ledger
Where the QuickBooks Online or Xero integration is on, invoices and payments were copied across, but time and expenses went only as invoice lines. The accounting package holds the receivables and Harvest holds the time behind them. Both are read, and the invoice numbers are used to match one to the other.
Archived clients and projects
Clients and projects that are finished can be archived instead of deleted, and archived records are easy to leave out of an export. The analysis counts active and archived records separately, and the firm chooses whether closed work comes across as closed matters or stays behind in the Harvest account.
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 Harvest 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 Harvest, 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 Harvest: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Harvest 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 Harvest as at the cutover date. Harvest 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 Harvest 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 Harvest 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
Harvest to Centerbase: what firms ask
Harvest has projects, not matters. How does that convert?
Each project becomes a matter under the same client, keeping its name and any code as the matter reference. Firms that used one long-running project per client, with all work logged to it, decide during clean-up whether to split it into separate matters or carry it as a single general matter.
Will our old time entries keep their notes?
Time entries are read with their date, person, project, task, hours, billable flag and the notes typed on them. In the new system the notes become the narrative on each entry. Entries already invoiced are linked to their invoice where the destination supports that, and listed as billed where it does not.
We have no trust records in Harvest. Is that a problem?
It is common. Harvest has no trust accounting, so client money has been tracked in the accounting package or a spreadsheet. Those records become the source for opening trust balances in the new system, and each one is agreed to the trust bank statement before it is loaded.
Does billing history from Harvest 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 Harvest. 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 Harvest have a place in Centerbase?
Most of it does on paper. Documents, custom fields and templates 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 Centerbase is kept as a readable archive, and you see which before the move.
What has to be decided before Harvest data is loaded into Centerbase?
Documents, 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 Harvest and into Centerbase
Other destinations from Harvest
Other systems that move 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.
Harvest and Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from Harvest 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.