Migrate your Centrium CRM data

Contacts are Centrium's primary object with unlimited records per account. We transfer all standard contact fields, the contact-company association, and any custom fields added through the field configuration panel. Phone number formatting is preserved across all export formats.

Centrium does not have a distinct Companies/Accounts object — organizations are stored as contact records with an organization flag. We identify these records during preprocessing and map them to the target CRM's Account/Company object, preserving the name and any stored address data.

Deals track pipeline stages from first contact to close with a status field (won/open/lost). We preserve the stage history as a chronological log and map stage names to the destination pipeline stages defined in the scoping phase.

Tasks support assignment to team members, due dates and completion status. We migrate open and completed tasks and preserve the assignee mapping using the target CRM's user records as the reference.

Centrium Projects are lightweight containers linking tasks and contacts. We transfer the project name, linked tasks and associated contacts. Any project metadata beyond name and membership requires a custom field map.

Notes are flat text records attached to contacts, deals or projects. We migrate the full note body and preserve the parent-object association. Notes are not threaded — multi-message conversations map as separate note records.

Custom fields are supported but stored in a simplified schema. We extract the field definition and values per record during the extract phase and apply a field-level map at import time on the destination side.

Files can be attached to contacts, deals and projects. Centrium exposes attachments through the UI but not through a documented public API. We flag attachments that cannot be retrieved via the UI export path and note which require manual re-upload.

User records include name, email and role permissions. We map source users to target users by email and flag any orphaned assignments where the source user has no match in the destination.

Centrium uses a team-level permission model without granular role definitions. This model does not map cleanly to RBAC systems in most destination CRMs. We treat permissions as a legacy constraint and do not attempt to replicate the permission set — all records land as owned by the importing admin account by default.

Centrium uses a fixed deal pipeline with three statuses (won/open/lost). If the destination has a multi-stage pipeline, we map the Centrium status to the nearest equivalent stage and flag the absence of intermediate stage history.

Reports in Centrium are pre-built summary views generated on-demand and are not stored as exportable data objects. We do not migrate historical report outputs — reporting must be rebuilt in the destination CRM using the migrated data.