Data migration route
Intapp to Centerbase migration
Intapp is a cloud specialist tool, and Centerbase is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Centerbase, often from a separate accounts package.
IntappCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Intake: Carried across
- Custom fields: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Templates: Confirmed in the analysis
CenterbaseCloud- 7 carried
- 1 mapped
- 4 to confirm
What moves
What moves from Intapp to Centerbase
Each row is a kind of record Intapp holds, whether Centerbase has a place for it, and what is planned. On this route seven kinds of record carry across, one kind needs mapping and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partNew business requests and their approvals, by client and matter. | Has a placeLoaded under their client, with practice-specific custom fields. | Carried across |
| ContactsClients, other parties and referrers | Held in partClient, engagement and relationship data in Conflicts and DealCloud. | Has a placeClients, related parties and prospects. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partClient guideline documents and vendor agreements in Intapp Terms. | 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 | To be confirmed | Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a place | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partApproval workflows, tasks and alerts tied to intake and client terms. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldIntapp Time captures time across devices. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | Held in partBillstream manages proforma review and approval. | 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 | HeldIntake request forms and workflows are built by each firm. | Has a placeCreated and placed on page layouts before records are loaded. | Carried with mapping |
| 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 |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntapp Intake runs client and matter onboarding; DealCloud holds 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 Intapp.
- 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.
- 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
Cases come across. The accounts are set up new.
A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to Centerbase brings those two sources together. The case records come from Intapp. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.
Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in Centerbase, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Intapp 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 Intapp is kept running until the checks on Centerbase are finished.
Where the data is now
Leaving Intapp
Nobody moves off Intapp as a whole. A firm replaces one product, or changes its practice system and finds that the Intapp products were fed by it. Either way the work starts by listing which products are licensed, what each holds that exists nowhere else, and which records are only copies of data owned by the finance system.
Name the product first
Intake, Conflicts, Walls, Terms, Time, Billstream and DealCloud each keep different records. A plan to move from Intapp means little until the product is named. The analysis opens with the list of products in use and whether each is on Intapp’s cloud or an earlier installation in the firm’s own environment.
Intake history
The Intake product holds each new business request with its answers, risk assessment and approvals. That is the firm’s evidence that a matter was opened properly. A practice system may take the client and matter but has no place for the approval trail, which is then kept as a document on the matter or in an archive.
Conflict search records
Conflicts brings client, engagement and relationship data together for searching and records the clearance of each search. The underlying names come from other systems and move with them. Clearance records do not, and the firm’s risk team decides how long it must stay retrievable and in what form.
Time before it is posted
The Time product captures time on phones and desktops and hands entries to the billing system. Entries still in draft, or captured but not released, may exist nowhere else. A cut-off is agreed so every timekeeper releases their time before the switch, and a count of unreleased entries is taken on the day.
Walls and who sees what
Walls sets information barriers once and enforces them across the firm’s other systems. When one of those systems is replaced, the restrictions have to be applied to the new one before any matter is opened to staff. The list of walled matters and their permitted teams is taken out early for that reason.
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 Intapp 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 Intapp, 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 Intapp: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Intapp 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 Intapp as at the cutover date. Intapp 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 Intapp 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 Intapp 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
Intapp to Centerbase: what firms ask
We are changing practice management system. What happens to our Intapp products?
They stay, but their connections change. Intake, Conflicts and Time work from the clients, matters and timekeepers in the practice system and write back to it. Each of those feeds is rebuilt against the new system and tested during the trial load, so new matters and time entries have a working route before go-live.
Can Intapp Time entries be moved into a practice system?
Released time normally already sits in the firm’s billing system, so it moves with that system. What needs attention is time still held in the capture tool. Timekeepers release it before the cut-off, and anything left is exported and loaded as unbilled entries against the right matters.
Is DealCloud covered?
DealCloud is Intapp’s relationship management product, used for contacts, pipeline and marketing. Moving it is a CRM migration in its own right. Contacts and their history are mapped to the new CRM or to the practice system’s contact records, and duplicates between the two lists are merged where they can be identified.
Does billing history from Intapp 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 Intapp. 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 Intapp have a place in Centerbase?
Most of it does on paper. Emails, notes, calendar entries 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 Intapp data is loaded into Centerbase?
Custom fields are carried with mapping, so each mapping is agreed with you first. Emails, notes, calendar entries 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 Intapp 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.
Intapp and Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from Intapp 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.