Migrate from Centrium CRM to Microsoft Dynamics 365 Sales

Standard Centrium Contact records with no organization flag map directly to Dynamics 365 Contact. All standard fields (name, email, phone, address, custom fields) transfer via the normalized CSV schema we build during extraction. Owner assignment resolves by email match against the destination User table, with unresolved owners flagged in the reconciliation report.

Centrium stores organizations as Contact records marked with an organization flag rather than a distinct object. We identify these records during preprocessing, deduplicate by organization name, create the corresponding Dynamics 365 Account records first, then re-link the individual Contact records with the resolved AccountId. This is the primary preprocessing step that can extend timeline for accounts with large organization lists.

Centrium Deals map to Dynamics 365 Opportunities. The Centrium status (won/open/lost) maps to the nearest Dynamics 365 Opportunity Stage — typically Open (or a custom first stage) for open deals, Won Closed for won, and Closed Lost for lost. Because Centrium stores no intermediate stage history, the single status field populates the initial stage only; the customer documents any additional stage progression for manual entry post-migration.

Centrium Tasks migrate to Dynamics 365 Task records. We preserve Subject, Description, Due Date (scheduledend), completed status (statecode), and priority. Assignee resolves by email match against Dynamics 365 User records. Completed and open tasks migrate — the migration does not filter by status.

Centrium Projects are lightweight containers linking tasks and contacts without a Dynamics 365 native equivalent. We assess the customer's project usage during discovery. For minimal use, we migrate project name and linked contacts as a Note on the related Account. For heavy project usage, we provision a custom AccountProject entity in Dynamics 365 with lookup to Account and Contact, and migrate project membership as project-team records.

Centrium Notes (flat text attached to contacts, deals, or projects) migrate to Dynamics 365 Note records. We preserve the note body, the original creation timestamp, and the parent-object association via the Regarding (objecttypecode + objectid) lookup. Notes are not threaded in Centrium and remain flat in Dynamics 365.

Centrium custom fields (added through the field configuration panel) extract as property-value pairs during the normalize step. We pre-create the corresponding custom fields in Dynamics 365 during the schema phase using the appropriate field type (text, number, picklist, date), then map values at import time. Custom field definitions are preserved in the field map delivered with the migration inventory.

Centrium attachments on contacts, deals, and projects are accessible through the UI but not through a documented API. We extract attachments where the UI export exposes them and attach them as Note records (for small files) or flag them for manual upload to a SharePoint Document Location linked from the parent Account or Contact. Large attachment volumes requiring SharePoint migration add scope to the migration timeline.

Centrium User records (name, email, role permissions) map to Dynamics 365 User records by email. We resolve active Centrium users to active Dynamics 365 users. Any Centrium user with no match in the destination org enters a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references on Contact, Account, and Opportunity require a valid User.