Migrate from Prophet CRM to Microsoft Dynamics 365 Sales

Prophet Contacts map directly to Microsoft Dynamics 365 Sales Contact records. The bidirectional Outlook contact sync must be frozen before extraction to prevent the sync from re-creating records during import. We resolve the EmailAddress1 field as the primary match key and set the ParentCustomerId lookup to the mapped Account once Companies land. Custom fields on Contact migrate to custom fields on Contact using the __c suffix, with field types mapped from the Prophet audit (text to single-line text, number to whole number or decimal, date to datetime).

Prophet Companies map directly to Microsoft Dynamics 365 Sales Account records. Standard fields including Name, Industry, Address, NumberOfEmployees, and AnnualRevenue export cleanly. We use Company Name as the Account Name and Company Phone as the main phone field. Account is created before Contact import so the ParentCustomerId lookup is satisfied at the moment of Contact insert.

Prophet Opportunities map to Microsoft Dynamics 365 Sales Opportunity with Name, EstimatedValue, CloseDate, and Probability preserved. Stage assignments migrate as part of the record and map to a Dynamics Sales Process configured before migration. Closed-Won and Closed-Lost reasons from Prophet custom fields map to standard Opportunity fields or custom fields on Opportunity.

Prophet pipeline stages are configurable per department, meaning stage names and counts vary across organizations. We capture the full stage list during the scoping audit, map each Prophet stage to a Microsoft Dynamics 365 Sales Stage in a Sales Process, and set the StageProbability to match the original Prophet stage probability. Stage mapping lives in a configuration table we deliver alongside the migrated data.

Prophet Activities include email tracking, tasks, appointments, and call logs linked to Contacts and Opportunities. There is no bulk export endpoint, so we extract via OData paginated queries in batches of 500-1,000, preserving the linked Contact or Opportunity reference. Emails migrate as EmailMessage records; tasks, appointments, and calls migrate as Task or Event records with the appropriate TaskSubtype set.

Prophet custom fields exist per object and per department template, meaning the effective schema varies by department even on the same object. We audit the complete custom field inventory during scoping, enumerate field names, data types, and which departments use which templates, then pre-create matching custom fields in Microsoft Dynamics 365 Sales before any data loads. Fields that exist in one department but not another are flagged and migrated only where data is present.

Prophet attachments on Companies, Contacts, and Opportunities store file metadata and URLs from the OData export. We extract attachment content where accessible, upload to Dynamics 365 SharePoint location or Dataverse file storage, and link via the Regarding field to the parent Account, Contact, or Opportunity record. Attachment migration depends on source data accessibility and is confirmed during scoping.

Prophet departments are first-class with custom templates and configurable cross-department access. We export department assignments on records and role-based settings as part of the migration scope. Microsoft Dynamics 365 Sales Business Units map the hierarchy, but Business Unit configuration is an admin task outside the data migration scope. We deliver a department-to-Business-Unit mapping table and the associated access rule inventory for the customer's admin to configure post-migration.