Migrate from Aurea CRM to HighLevel

Aurea CRM Contact records map 1:1 to GoHighLevel Contact objects via the REST API. We extract standard contact fields (name, email, phone, address) through the Import/Export module and load via GoHighLevel's contact upsert endpoint. Email serves as the dedupe key. Custom contact fields migrate to GoHighLevel custom contact fields, which we pre-create in the destination account before import. Owner (assigned Aurea CRM user) maps to GoHighLevel assigned user by email match; unresolved owners are flagged in the reconciliation report.

Aurea CRM Account (Company) records map to GoHighLevel Location objects, which serve as the organizational record linked to Contacts. We preserve the parent-child relationship between Accounts and Contacts by loading Locations first, then resolving the location_id reference on each Contact during import. The Aurea CRM account name becomes the Location name, and the primary address fields map to GoHighLevel Location address fields.

Aurea CRM Opportunity records map to GoHighLevel Pipeline Deals. The Aurea deal stage name maps to the corresponding GoHighLevel Pipeline stage value; we create the pipeline and stage configuration in GoHighLevel before migration to ensure stage keys are available for mapping. Deal value, probability, and close date migrate to the GoHighLevel Deal amount, stage probability, and close date fields. We preserve Aurea's pipeline assignment by creating a GoHighLevel Pipeline for each Aurea pipeline.

Aurea CRM activity records (tasks, appointments, timeline entries) map to GoHighLevel Task objects. Activity type determines the mapping: Aurea task-type activities become Tasks with the original timestamp preserved, and Aurea appointment-type activities become Tasks with date and time fields mapped. Activity descriptions migrate as task notes. We resolve the parent Contact or Location reference using email and company name matching against the already-migrated GoHighLevel records.

Aurea CRM partner records track channel partner leads and opportunities with partner-specific quota and territory assignments. These map to GoHighLevel Locations (for partner organizations) or Contacts (for individual partner representatives) depending on the customer's data model. Partner-specific quota and territory data migrates as custom fields on the Location because GoHighLevel does not have a native territory management object. We flag partner portal data that cannot map cleanly and document it for the customer admin to restructure post-migration.

Aurea CRM Campaign Manager records (campaign type, status, and response metrics from the Enterprise bundle) map to GoHighLevel Campaign objects. Campaign name, status, start and end dates, and budgeted cost migrate directly. Aurea-specific campaign workflow triggers and response tracking do not map to GoHighLevel's campaign model; we preserve campaign membership data as GoHighLevel Campaign members and document the workflow gap for rebuild in GoHighLevel's Workflow builder.

Aurea CRM administrator-added custom fields across all objects migrate to GoHighLevel custom fields of equivalent type. We catalog every custom field during discovery, pre-create the corresponding GoHighLevel custom field (with correct type: text, number, date, picklist, or checkbox), then map values during the data transform phase. Complex picklist values require explicit value mapping where Aurea picklist options differ from GoHighLevel allowed values.

Aurea CRM user records map to GoHighLevel User accounts by email. We extract all distinct owners referenced on Contact, Account, Opportunity, and Activity records, match by email against GoHighLevel Users, and flag any Aurea owner without a GoHighLevel User match in the reconciliation report. The customer admin provisions any missing GoHighLevel Users before record import continues because OwnerId is a required reference on Deals and Contacts.