Migrate from Aurea CRM to Salesforce Sales Cloud

Aurea Contact records migrate 1:1 to Salesforce Contact. We extract all standard contact fields via the Import/Export module and resolve the parent AccountId by matching the Contact's associated Company record against the migrated Account. Email and Name serve as the primary dedupe keys. Any custom contact fields are catalogued during discovery and mapped to Salesforce custom fields before import begins.

Aurea Account (Company) records map directly to Salesforce Account. The parent-child relationship between Account and Contact is preserved by creating Accounts first during migration, then resolving the AccountId lookup on each Contact record at insert time. Company ID from Aurea is preserved as an external reference field for audit purposes.

Aurea Opportunity records map to Salesforce Opportunity. Stage names are explicitly mapped because Aurea's pipeline stages are configurable per installation and must be matched to the customer's Salesforce Sales Process. We create the Salesforce Sales Process and stage probability values during schema design before any Opportunity data is loaded. CloseDate, Amount, Probability, and OwnerId migrate directly with parent AccountId resolution.

Aurea activity records (tasks, appointments, and timeline entries) map to Salesforce Task and Event objects. Aurea's configurable activity types are reviewed during discovery; legacy subtypes that do not map directly to Task or Event are flagged and mapped to the nearest Salesforce equivalent. Task and Event records are loaded via the Salesforce Bulk API 2.0 with parent-record lookup resolution (WhoId, WhatId, AccountId) to preserve the activity timeline against the correct Contact and Opportunity.

Aurea Campaign Manager campaign records — including campaign type, status, and response metrics — map to Salesforce Campaign. Some Aurea-specific campaign workflow fields do not have direct Salesforce equivalents; these are flagged and preserved as custom fields for the customer's admin to configure. CampaignMember records linking Contacts to Campaigns migrate as Salesforce CampaignMember with Status mapped from Aurea's response tracking.

Aurea Partner records (including partner-specific quota and territory assignments from the PRM module) require explicit field-level mapping. The destination structure depends on whether the customer licenses Salesforce Partner Relationship Management on Enterprise or Unlimited; if not, we map Partner records to a Salesforce custom object with territory and quota fields as custom properties. The mapping strategy is confirmed during scoping.

Aurea document management stores files linked to records. We migrate documents as ContentDocument records with ContentDocumentLink associations to the parent Contact, Account, or Opportunity when the Aurea file store is accessible. Records with high attachment volume are flagged for manual review because large binary exports can cause timeouts during batch extraction.

Aurea administrators can add custom fields across all objects. We catalog all active custom fields during discovery, map them to Salesforce custom properties with appropriate field types (text, number, picklist, date, checkbox), and pre-create the destination schema before any data import begins. Fields with complex picklist value dependencies or cross-object references are flagged for manual configuration review.

Aurea CRM workflows configured via the Aurea CRM Automator are application configuration, not data records, and do not appear in standard exports. We document active workflows during discovery by reviewing CRM.designer configuration and deliver a written workflow reconstruction guide mapped to Salesforce Flow equivalents (record-triggered, scheduled, or screen flow). The customer's admin rebuilds them post-migration.

CRM.cockpit is an add-on dashboard and KPI visualization module bundled with Aurea CRM Enterprise. Dashboard configurations are application configuration, not data records, and do not export. We capture screenshots and field references from the customer's live CRM.cockpit setup and deliver a written guide for rebuilding equivalent reports and dashboards in Salesforce Reports and Dashboards or Einstein Analytics.

Aurea user and owner records migrate as the assignee dimension for all owned records (Contact, Account, Opportunity, Activity). We map Aurea user IDs to Salesforce User accounts by email match. Any Aurea Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Territory assignments and quota values from Aurea CRM require explicit field-level mapping. The data model structure differs significantly between Aurea and Salesforce, so we extract territory and quota fields as custom properties and reconstruct them in Salesforce either through native Territory Management (Enterprise/Unlimited) or a custom forecast quota object. Mapping strategy is confirmed during scoping.

Aurea Campaign Manager bundled with Enterprise has its own campaign workflow configuration. This is application configuration and does not migrate. We document the Aurea Campaign Manager setup (campaign types, automated rules, response workflows) and provide a written guide for rebuilding equivalent email marketing automation in Salesforce Marketing Cloud Account Engagement (Pardot) or Marketing Cloud, depending on the customer's marketing stack decision.