Migrate your Centerbase data

Matters are the central organizing entity in Centerbase, containing client relationships, billing records, documents, and time entries. Standard matter fields and most custom fields map cleanly; we preserve matter status, responsible attorney, and practice area as primary migration targets.

Client records in Centerbase function as the account-level entity above Matters. We map them to contacts or account objects in the destination, preserving client-level billing settings, location codes, and contact information.

Contact records store party information on Matters and are used for communications and calendar associations. Standard contact fields including addresses, phones, and emails transfer directly; custom contact properties require field-level mapping.

Time entries link to Matters and carry billing codes, origination data, and hourly rates. We sequence time entries in chronological order and preserve the full billing hierarchy so trust, expense, and fee slips reconstruct correctly in the destination.

Bills in Centerbase carry a complex structure including pre-bill workflows, billing codes, LEDES formatting, AR thresholds, and trust allocation. We extract all line items and present them for mapping because billing format expectations differ significantly between systems.

Documents attach to Matters and Clients. Centerbase's export explicitly notes that images do not transfer; we flag document attachments that will require manual re-association post-migration or secondary file transfer mechanisms.

Trust accounts track IOLTA holdings, operating transfers, and client-specific trust balances. Centerbase stores trust at the matter level with specific ledger rules. We map trust balances and transaction history but note that three-way reconciliation rules must be re-established at the destination.

Workflows in Centerbase range from basic step-by-step automation to advanced triggers on record creation or field updates. Because workflow logic is platform-specific and often rebuilt from scratch on new systems, we document all active workflow definitions as part of migration scoping.

Centerbase supports custom objects for firm-specific data structures. These require schema discovery and field-level mapping because the destination system may not have equivalent custom object definitions.

Activities and calendar entries link to Matters and Contacts. Centerbase migration documentation confirms that calendar entries transfer from Time Matters; we include them in migration scoping with calendar date and matter association preserved.

Reports can be exported and imported between Centerbase databases as definition files, but they require matching fields in the target system. We include report definitions in scoping and flag any report that references fields not present in the destination schema.

User profiles in Centerbase include role assignments, login credentials, and billing rate tables. We map active users to owner fields in the destination and flag any inactive or archived users for explicit customer decision.

Accounts Payable tracks vendors and outstanding payments. We include vendor records in the migration scope, mapping to the destination's vendor or supplier object while noting any open AP balances that require reconciliation.