Migrate from Aurea CRM to Microsoft Dynamics 365 Sales

Aurea CRM Contact records map 1:1 to Microsoft Microsoft Dynamics 365 Sales Contact. Standard fields (name, email, phone, address) transfer directly. The Aurea Contact's parent Account reference resolves to a Dynamics 365 Account lookup at migration time. Custom fields cataloged during discovery map to Dataverse custom columns. If Aurea contacts lack an Account association, they import as standalone Contacts for the customer admin to associate post-migration.

Aurea CRM Company records (the Account object equivalent) map 1:1 to Dynamics 365 Account. The Company name becomes Account Name, domain fields map to Website, and address fields map using the Dynamics 365 composite address model. Account is created before Contact import so that the parent AccountId lookup is satisfied at Contact insert time.

Aurea CRM Opportunity records map to Dynamics 365 Opportunity. The Aurea pipeline stage label (configurable per installation) maps to a Microsoft Dynamics 365 Sales Process stage value that we configure in the destination org before migration. Estimated value, close date, probability, and probability percentage migrate to EstimatedValue, CloseDate, and StageName fields. Any Aurea-specific probability settings migrate to custom Opportunity fields.

Aurea CRM's pipeline stage definitions map to Dynamics 365 Record Types on Opportunity, each with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate to the Sales Process stage probability mapping. If the source Aurea installation uses multiple pipelines (Enterprise feature), each pipeline becomes a separate Record Type in Dynamics 365.

Aurea CRM activity records split into Tasks (with TaskSubtype preserved where applicable) and Events (with StartDateTime and EndDateTime preserved). The parent record reference resolves to Dynamics 365 Contact, Account, or Opportunity via the lookup chain. Legacy activity subtypes that do not have a direct Dynamics 365 equivalent are migrated as Task records with the original activity type preserved in a custom field for admin reference.

Aurea Campaign Manager data (campaign type, status, and response metrics) migrates to Dynamics 365 Campaign. Campaign responses migrate to CampaignResponse records. Some Aurea-specific campaign workflow fields (such as Automator-triggered campaign actions) do not transfer as automation and are documented separately in the workflow reconstruction guide.

Aurea CRM partner records include partner-specific quota, territory assignments, and portal data that require explicit field-level mapping. If Microsoft Dynamics 365 Sales Partner Center is in use, partners migrate as Account records with the PartnerType field set; otherwise partners migrate to a custom Dataverse table created before migration to preserve partner-specific quota and territory data that does not fit standard Account fields.

Aurea CRM custom fields across all Info Areas are cataloged during discovery. Each custom field maps to a Dataverse custom column of the equivalent type (text, integer, decimal, datetime, picklist). Picklist values migrate as Option Set values in Dynamics 365. Any Aurea-specific picklist labels are mapped explicitly to their Dynamics 365 Option Set labels during transform.

Document management in Aurea CRM stores files linked to records. If the Aurea file store is accessible, we migrate documents as SharePoint files attached to the corresponding Dynamics 365 Account, Contact, or Opportunity via the native SharePoint integration. If the file store is not accessible, documents are flagged for manual handoff and we document which records had high attachment volume.

Aurea CRM users migrate as the assignee dimension for all owned records. We map Aurea user IDs to Dynamics 365 User accounts by email match. Any Aurea user without a matching Dynamics 365 User is held in a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId references on Opportunity, Task, and Campaign must be resolved before those objects import.

Territory assignments and quota values from Aurea CRM map to Dynamics 365 Territory records if the Sales Enterprise or Premium tier is licensed. If only Professional tier is licensed (which does not include Territory Management), we migrate the data to a custom Dataverse table and document the Territory configuration for the admin to set up post-migration.