Migrate from Centrium CRM to Pipedrive

Centrium Contact records map directly to Pipedrive Person. All standard contact fields (name, email, phone, address, social media) migrate as typed fields. Custom fields defined in Centrium's field configuration migrate as Pipedrive custom fields, which must be pre-created in the destination account before import because Pipedrive's API requires the field to exist before a value can be set. Owner assignment resolves by email match against the Pipedrive user table; any Centrium owner without a matching Pipedrive user is flagged in the reconciliation report for admin provisioning before record import.

Centrium does not have a dedicated Companies or Accounts object. Organizations are stored as Contact records with an organization flag. During preprocessing, we identify all contacts marked with this flag, create corresponding Organization records in Pipedrive (using the contact's company name as the Organization name), then re-link the individual Contact records by setting the Organization ID on each Person record. This preprocessing step adds one to two days to the migration timeline for accounts with large organization lists and must complete before the Person import phase begins so that the Organization ID lookup is satisfied at insert time.

Centrium Deals map to Pipedrive Deals with the deal title, value, expected close date, and status (won/open/lost) preserved. The Centrium status maps to the nearest Pipedrive pipeline stage during the field-mapping phase. Pipedrive's multi-stage pipeline structure is configured during the destination schema setup — if the customer uses only Centrium's three-status model, we create a matching single-stage pipeline in Pipedrive to avoid forcing a pipeline redesign on day one. Deal custom fields migrate as Pipedrive deal custom fields, pre-created before the deal import phase.

Centrium's deal pipeline uses a fixed three-status model (won/open/lost). We map each Centrium status to the nearest equivalent Pipedrive stage during schema setup. If the customer uses any custom stage names in Centrium, we carry those into Pipedrive as custom stage labels rather than forcing a rename. Stage probabilities in Pipedrive default to standard values for won and lost and the customer's chosen probability for the open stage. Stage order maps directly from Centrium's pipeline ordering.

Centrium Tasks migrate to Pipedrive Activity records with the activity type set to Task, the due date preserved, the completion status mapped to Pipedrive's done flag, and the assignee resolved by email match against Pipedrive users. Open tasks and completed tasks both migrate — completed tasks retain their completion timestamp and are visible in Pipedrive's Activity timeline. The task body (description) migrates as the activity note field. Orphaned assignments where the Centrium owner has no Pipedrive user match are flagged for manual assignment after migration.

Centrium Projects are lightweight containers linking tasks and contacts. Pipedrive's Projects module (available from Growth plan) receives the project name, linked tasks, and associated contacts. Project metadata beyond name and membership (such as project status or project-level custom fields) is limited by what Centrium exposes in its export. We note any project fields that cannot be transferred in the scoping document before migration begins. If the destination Pipedrive account is on the Lite plan, we flag that Projects requires an upgrade before this object can be imported.

Centrium Notes are flat text records attached to contacts, deals, or projects. They map to Pipedrive Activity records with the activity type set to Note. The parent-object association migrates as a link to the corresponding Pipedrive Person, Organization, or Deal. Notes in Centrium are not threaded — multi-message conversation threads map as separate sequential Note records in Pipedrive rather than a single thread. This is a structural difference that we disclose in the validation report.

Centrium user records (name, email, team membership) map to Pipedrive users by email address. We resolve each Centrium user referenced on any record to a Pipedrive user by email match. Any Centrium user with no corresponding Pipedrive user goes to a reconciliation queue — the customer's Pipedrive admin must provision the missing users before the migration resumes. We do not set permissions in Pipedrive as part of the migration because Centrium's team-level permission model has no RBAC equivalent to transfer.

Centrium custom fields (text, number, date, URL types) migrate as Pipedrive custom fields of the matching type. We extract the field definition from the Centrium export during the preprocessing phase and provision the corresponding custom field in Pipedrive via the API before any record import begins. Multi-select picklist values in Pipedrive are supported as a target type; single-select picklists map from Centrium category fields. This step must complete before Person, Deal, or Activity import so that the API accepts the field values on insert.

Centrium attachments are files linked to contacts, deals, and projects. Since Centrium exposes attachments through the UI but not through a public API, we cannot retrieve file binaries programmatically. We flag the total count and size of attachments during the discovery call and note them in the scoping document. The customer must either manually download attachments from the Centrium UI and re-upload them to Pipedrive after migration, or archive them externally. This is a manual post-migration step, not a migration automation gap.