Migrate from Aurea CRM to Freshsales

Aurea Contact records map to Freshsales Lead or Contact depending on qualification status. We assess the Aurea contact record's status field, partner flag, and any custom lifecycle properties during scoping to determine the split rule. Qualified leads (with active deal associations or recent activity) map to Freshsales Contact; unqualified prospects map to Lead. The original Aurea contact status is preserved in a custom field aurea_contact_status__c on both Lead and Contact for audit trail and reporting continuity.

Aurea Account (Company) records map directly to Freshsales Account. The Account Name, Website, Industry, Annual Revenue, Phone, and Address fields migrate 1:1. Account is the parent record for Contact, so we insert Accounts before Contacts in the migration sequence to satisfy the AccountId lookup. Aurea partner organizations flagged in the PRM module require custom handling: if the partner has both a company record and individual contacts, we map to Account and Contact with a custom partner_type__c field set to 'Partner' and territory information preserved in custom fields.

Aurea Opportunity records map to Freshsales Deal. The Opportunity name, value, stage, probability, close date, and owner migrate 1:1. Aurea pipeline stages are configurable per installation and must be mapped explicitly to Freshsales Deal stages. We create the Freshsales pipeline and stages before migration so that stage names match the Aurea source during import. Probability percentages transfer to the stage configuration in Freshsales.

Aurea activity types are configurable and may include subtypes that do not map directly to Freshsales standard activity types. We catalog every distinct Aurea activity subtype during discovery and map them to the closest Freshsales type: tasks map to Task, scheduled meetings map to Event, logged phone calls map to Call, and remaining subtypes map to Task with a custom activity_subtype__c field carrying the original Aurea value. Activity records linked to Contacts and Accounts carry the parent record's Freshsales ID resolved at migration time.

Aurea Campaign Manager records (Enterprise tier) include campaign type, status, response metrics, and budget information. These map to Freshsales Campaign object. Aurea-specific workflow fields on campaigns (such as campaign stage automation triggers) do not migrate as automation rules; they are preserved as campaign metadata fields and documented for rebuild in Freshsales Workflows. If the customer does not license Freshmarketer, campaign-level email automation is documented separately for Freshsales Workflow design.

Aurea Partner relationship management records track channel partner leads, partner-specific quota assignments, and territory data. Freshsales has no native PRM object. We handle this in one of two ways based on customer scope: as a Freshsales custom object (Partner__c) with lookup to Account, or as additional custom fields on the Account record with a partner_type__c flag. Partner quota and territory assignments migrate to custom fields. We confirm the preferred approach during scoping.

Aurea document management stores files linked to records. We migrate document attachments where the Aurea file store is accessible via the export. Files are imported as Freshsales attachments linked to the parent Contact, Account, or Deal. Records with high attachment volume (over 50 attachments per record) are flagged for manual review to confirm file accessibility before migration begins.

Aurea CRM custom fields are catalogued during discovery across all Info Areas. We map each custom field to a Freshsales custom property of the equivalent data type: text fields to TEXT, numeric fields to NUMBER, date fields to DATE, and picklist fields to DROPDOWN. Complex picklists with multi-select behavior map to Freshsales multi-select fields. The custom field API name in Freshsales follows the source field label converted to a sanitized format.

Aurea user records migrate as the Owner dimension for all owned records. We resolve Aurea user IDs to Freshsales User accounts by email match. Any Aurea user without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import. Owner assignments on Contacts, Accounts, and Deals migrate once the User mapping is validated.