Migrate from Centerbase to Twenty CRM

Centerbase Clients map directly to Twenty People. Every Client record becomes a Person record with the Client's name, email, phone, and address fields transferred. Clients without email receive a placeholder email flagging them as migrated from Centerbase.

A Centerbase Client can have multiple Contact records (primary attorney, billing contact, paralegal). Each Contact migrates as a separate Twenty Person record linked to the same Company (client firm) record. We preserve the contact type as a custom select field on each Person.

Centerbase Company records (the opposing party or vendor organizations, not client firms) map 1:1 to Twenty Companies. Company name, domain, industry, employee count, and address fields transfer directly. Multi-company contacts in Centerbase collapse to a primary CompanyId in Twenty.

Centerbase Matters have no native equivalent in Twenty's Opportunity object. We create a custom Matter object in Twenty mirroring Opportunity fields plus matter-specific properties: matter number, responsible attorney, originating staff, matter type, and status. Matter number is set as a unique field for import matching.

Centerbase matter statuses (Open, Pending, Closed, On Hold) map to Twenty Opportunity stage values on the custom Matter object. Stage labels are mapped value-by-value. Probability weights are assigned based on your firm's historical stage-to-close rates — your admin confirms the mapping before the migration runs.

Centerbase billing entries (hourly time slips, fixed fees, expenses) require a custom BillingEntry object in Twenty with fields for date, hours, rate, amount, matter link, and billing status. Trust accounting entries (IOLTA transfers) are tracked separately as trust-specific custom fields within this object.

Centerbase invoices migrate as a custom Invoice object linked to the Matter and BillingEntry records. Invoice number, date, total, balance due, and payment status transfer. LEDES billing code metadata is preserved in a custom text field for reference.

Centerbase activities map to Twenty Tasks. Call logs, emails, and notes transfer with original timestamps, owners, and parent record links (People, Company, or Matter). Meeting records become Twenty Tasks with the meeting subject and duration preserved.

Centerbase documents attached to matters, clients, or contacts are downloaded and re-uploaded to Twenty's file storage linked to the corresponding record. File name and original upload date are preserved. Image files embedded in rich-text notes are extracted and re-hosted as separate file attachments.

Centerbase custom fields on any standard object map to Twenty custom fields on the equivalent object or custom object. Field type mapping: text→text, number→number, date→date, picklist→select, checkbox→boolean. Multi-select picklists in Centerbase map to Twenty multi-select fields.

Centerbase users are resolved by email match against Twenty Workspace Members. Unmatched users are flagged before migration — your team either invites them to Twenty first or assigns their records to a fallback member. User name and role are preserved as custom fields on each matched member record.

Centerbase location codes (billing jurisdiction tags) migrate as a custom text field on the Matter object. If your firm uses a controlled vocabulary of location codes, we map them as a select field in Twenty instead.

Centerbase parent-child matter hierarchies map as a self-referential custom field on the custom Matter object: ChildMatter.ParentMatterId points to the parent's unique Matter number. Circular hierarchy references are flagged and resolved before import.