Migrate your Aurea CRM data

Aurea CRM's Contact records are the primary individual customer entity. We extract all standard contact fields via the Import/Export module or web-service endpoints and map them 1:1 to the destination Contact object, preserving email, phone, address, and ownership assignments.

The Account (Company) object holds organizational records linked to multiple Contacts. We preserve the parent-child relationship between Accounts and Contacts during migration to maintain account-level rollup reporting.

Opportunities track deal records through pipeline stages with value and probability fields. We map stage names explicitly since Aurea's pipeline stage labels are configurable per installation and must be aligned with the destination CRM's stage definitions.

Activities include tasks, appointments, and timeline entries. Aurea's activity types are configurable and some legacy activity subtypes may not map directly to standard CRM activity objects. We preserve date, assignee, and description fields and flag custom activity types for manual review.

Campaign records include Aurea Campaign Manager data such as campaign type, status, and response metrics. These map to the destination CRM's campaign object, though some Aurea-specific campaign workflow fields require custom field mapping.

Partner relationship management records track channel partner leads and opportunities. The partner portal data — including partner-specific quota and territory assignments — requires explicit field-level mapping because most destination CRMs do not have a native PRM object.

Document management in Aurea CRM stores files linked to records. We migrate documents as attachment references where the file store is accessible, or flag records with high attachment volume for manual document review during cutover.

Aurea CRM allows administrators to add custom fields across objects. We catalog all custom fields during discovery, map them to destination CRM custom properties, and flag any fields with complex picklist or conditional logic for manual verification.

Aurea CRM workflows (configured via the Aurea CRM Automator) are process-driven rules that do not export as data records. Workflow logic must be rebuilt manually in the destination CRM using equivalent automation tools. We document the workflow sequence and conditions to support reconstruction.

CRM.cockpit is a visualization and KPI dashboard module available as an add-on. Dashboard configurations are not data records and do not export. We capture screenshots and field references from the cockpit during discovery to support manual dashboard recreation.

User and owner records are migrated as the assignee dimension for all owned records. We map Aurea user IDs to destination CRM user accounts and preserve assignment history where the destination supports it.

Territory assignments and quota values are configurable within Aurea CRM. These map to destination CRM territory or forecast quota objects, though the data model structure varies significantly between platforms.