Data migration route
Claris FileMaker Pro to Centerbase migration
Claris FileMaker Pro is a desktop database, and Centerbase is a cloud practice management system. Before anything moves into Centerbase, the tables in Claris FileMaker Pro have to be read and explained.
Claris FileMaker ProDesktop- Documents: Carried across
- Custom fields: Carried with mapping
- Matters: Confirmed in the analysis
- Contacts: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
CenterbaseCloud- 1 carried
- 1 mapped
- 12 to confirm
What moves
What moves from Claris FileMaker Pro to Centerbase
Each row is a kind of record Claris FileMaker Pro holds, whether Centerbase has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping and twelve kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | To be confirmedDepends entirely on what the firm built. | Has a placeLoaded under their client, with practice-specific custom fields. | Confirmed in the analysis |
| ContactsClients, other parties and referrers | To be confirmedMost firm-built systems start with a client table, but it is confirmed per system. | Has a placeClients, related parties and prospects. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | Held in partContainer fields can hold files, embedded, stored externally or by reference. | 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 | To be confirmed | Has a place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a place | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | Has a placeThe vendor says billing history can be migrated; the depth is set in the analysis. | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeMultiple trust and retainer accounts per matter or client. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | Has a placeGeneral ledger with chart of accounts; opening trial balance agreed with the accountant. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldEvery table and field was defined by the firm or its developer. | Has a placeCreated and placed on page layouts before records are loaded. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmedLetters may be produced from layouts with merge fields; confirmed per system. | Has a place in partTemplates are rebuilt to merge Centerbase client and matter data. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis. | 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 Claris FileMaker Pro.
- 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
A home-built database, read table by table.
A database like Claris FileMaker Pro has no standard layout. Someone at the firm, or a contractor long gone, decided what the tables are and how they join. The analysis starts by reading that structure and writing it down in plain terms: this table is clients, this one is matters, this column is the fee earner. The firm confirms the reading before any mapping to Centerbase is proposed, because one wrong guess about a join misplaces every record that depends on it.
Home-built systems hold free text where a product would hold a field: a status typed six different ways, dates in whatever form the person entering them preferred. These are put into one format during clean-up, and the values that cannot be interpreted are listed. Documents are usually on a file share beside the database, linked by a path stored in a table. Each path is tested, and missing files are reported, before the documents are loaded.
Claris FileMaker Pro runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Centerbase is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Claris FileMaker Pro
With a firm-built system there is no vendor manual describing the data, so the first job is to write one. The design is read out of the FileMaker files themselves, then walked through with the person who knows the system best. Only after that can anyone say what it holds, which parts are still used, and where each field will go.
Read the design from the file
FileMaker can produce a Database Design Report, or save a copy of the file as XML, setting out every table, field, relationship, layout and script. Either needs an account with full access privileges. That report is the starting document for the analysis, and it can turn up tables nobody remembers.
Layouts are not tables
Staff know the system by its screens. A single matter layout may draw on five related tables through portals and lookups. Exports run table by table, so each screen is traced back to the tables behind it and the key fields that join them are carried through, or the links are lost.
Documents in container fields
A container field can hold a document embedded in the database, stored in an external folder that FileMaker manages, or only as a reference to a file elsewhere. Each kind is extracted differently. References are tested, because a path recorded in 2012 may point to a server that no longer exists.
Calculated and summary fields
A matter balance or total hours shown on screen may be a calculation, not stored data. An export gives the result as it stood that day. The firm chooses between bringing the figure as a fixed number and bringing the underlying entries so the new system can work it out again.
Free typing and private conventions
Home-built systems rarely validate what is typed. The same court appears under six spellings, dates sit in text fields, and one field has been reused for something else since 2015. Clean-up therefore takes longer here than for a packaged product, and the firm sees the proposed standard values first.
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.
No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Centerbase, they get a rehearsed cutover of their own.
Analysis
We read what Claris FileMaker Pro holds and how it is organised, then agree with you where each kind of record will sit in Centerbase. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into Centerbase and checked against Claris FileMaker Pro: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
After a short freeze on changes in Claris FileMaker Pro, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. Claris FileMaker Pro 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 Claris FileMaker Pro 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 Claris FileMaker Pro 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
Claris FileMaker Pro to Centerbase: what firms ask
The person who built our system has gone. Can it still be moved?
Usually, provided someone holds a full access account for the files. With that, the design can be read without the developer. Without it, data can still be exported from whatever the firm’s own logins can see, but the scripts and hidden tables cannot be inspected, and the analysis takes longer and says so.
Our system does things no legal product does. What happens to those?
Each one is listed in the analysis and put in one of three groups: the new system does it differently, the new system can be configured to do it, or it will stop. The third group is the one to discuss with the partners early. A custom register can also be kept as an exported spreadsheet.
Can we keep FileMaker for reference afterwards?
Yes. The files can be left on the server, or a copy opened in FileMaker Pro on one PC, with accounts changed to read only so nothing new is entered. That is the fall-back record. It depends on keeping a working FileMaker licence and a machine that runs it, which the firm should note for later years.
Do documents from Claris FileMaker Pro keep their folders and dates in Centerbase?
Centerbase stores documents. Into Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
Does everything in Claris FileMaker Pro have a place in Centerbase?
Most of it does on paper. Matters, contacts, emails, notes, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, templates and intake records 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 Claris FileMaker Pro data is loaded into Centerbase?
Custom fields are carried with mapping, so each mapping is agreed with you first. Matters, contacts, emails, notes, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, templates and intake records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Claris FileMaker Pro and into Centerbase
Other destinations from Claris FileMaker Pro
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.
Claris FileMaker Pro and Centerbase are the names and marks of their owners, used here only to identify the two systems.
Moving from Claris FileMaker Pro 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.