Migrate from Centerbase to Pipedrive

Centerbase Contact maps directly to Pipedrive Person. All standard contact fields (name, email, phone, address, job title) translate field-for-field. The primary organization link maps to the Pipedrive Person.org_id lookup. Contacts without a primary organization are imported without an org link and can be associated manually or via a post-migration deduplication pass.

Centerbase Organization maps to Pipedrive Organization with all standard company fields (name, domain/website, address, industry, employee count, revenue) migrating as direct equivalents. Multi-address records in Centerbase are preserved as address fields on the Organization; additional addresses are noted in a custom field for manual cleanup post-migration.

Centerbase Matter is the primary entity and maps to Pipedrive Deal. The matter name becomes the deal title, and the matter amount or billing amount maps to the deal value. Pipedrive has no native legal accounting model — matter status, billing codes, client ID, trust references, responsible attorney, origination attorney, and billing attorney all require pre-created custom fields in Pipedrive before migration. Matter stage values must be mapped to Pipedrive stage names explicitly.

Centerbase activities (calls, emails, meetings, tasks) map to Pipedrive Activities with subject, timestamp, owner, and linked record preserved. Centerbase activity records tied to both a matter and a contact are linked to the corresponding Pipedrive Deal and Person during migration. Note content migrates to Pipedrive Activity notes. Original activity timestamps are preserved in Pipedrive's created_at field.

Files and documents from Centerbase are exported where accessible and re-uploaded to the corresponding Pipedrive record (Person or Deal). Pipedrive enforces a 150MB file size limit per upload — files exceeding this are flagged for manual splitting or alternative file management. Centerbase's document management system (with folder hierarchy) has no direct Pipedrive equivalent; folder structure is lost and documents are re-attached to their related Pipedrive record without folder context.

Centerbase users and staff are resolved to Pipedrive users by email address matching. Each unique email in Centerbase is checked against Pipedrive user accounts — matched users become deal owners in Pipedrive. Unmatched users are flagged before migration so your team can create their Pipedrive account or assign a fallback owner before the migration runs. Attorney and staff roles are preserved as custom text fields on Deals since Pipedrive has no matter-role concept.

Centerbase custom fields on matters, contacts, and organizations map to Pipedrive custom fields on the corresponding object (Deal, Person, or Organization). Centerbase exposes custom field keys in its API — these keys are included in the migration mapping plan so Pipedrive custom fields can be pre-created with matching keys before migration. Pipedrive's custom field key system uses a hash identifier that requires pre-creation; FlitStack AI provides the key mapping table during the schema setup phase.

Centerbase's billing entries and trust accounting records are deeply integrated into its legal accounting engine with no Pipedrive equivalent. Pre-bill amounts, trust balance, IOLTA account, and billing codes are migrated as custom fields on the Deal for reference. Full accounting reconciliation requires a separate migration to dedicated accounting software. We document the billing data available for export and flag what requires rebuild in your target accounting platform.