Migrate from Aurea CRM to Pipedrive

Aurea Contact records map 1:1 to Pipedrive Person records. Standard fields (name, email, phone, address, title) map directly. The Aurea Contact's linked Account (Company) resolves to a Pipedrive Organization that must exist before the Person import begins. Custom contact fields migrate to Pipedrive custom fields on Person.

Aurea Account records map 1:1 to Pipedrive Organization. The Aurea Account name becomes the Organization name, and the account address maps to the Organization address fields. Organization is imported first so that the Person import can satisfy the organization_id foreign key by matching Organization name or a pre-seeded external_id.

Aurea Opportunity records map to Pipedrive Deals. The Aurea pipeline stage name maps to a Pipedrive Pipeline stage, and the deal value maps to Pipedrive's weighted value fields. We explicitly map Aurea's configurable stage labels during scoping because Aurea pipeline stages are named per installation. If the destination Pipedrive pipeline stages do not match Aurea's, we create custom stages before import.

Aurea pipeline stages are administrator-defined per installation and must be matched to Pipedrive pipeline stages during scoping. We query the Aurea administrator's pipeline configuration, then create or configure Pipedrive pipeline stages with matching labels and probability values. Stage probability percentages from Aurea migrate to Pipedrive stage probability settings.

Aurea Activity records — including tasks, appointments, and timeline entries — map to Pipedrive Activity records. Aurea's configurable activity subtypes (call, meeting, task, note) map to Pipedrive Activity types (call, meeting, todo, email). Activity dates, assigned users, and linked records (Contact, Account, Opportunity) migrate with the relationship preserved through Pipedrive's deal_id and person_id foreign keys. Some legacy Aurea activity subtypes may require transformation to the nearest standard Pipedrive type during staging.

Aurea Campaign Manager records (campaign type, status, response metrics, budget, and dates) map to Pipedrive Campaign records. Aurea campaign workflows — which are application configuration and not data records — are documented separately in the automation rebuild guide and do not migrate as data. Campaign members from Aurea are not a standard data structure in all installations; if present, we map them to Pipedrive Campaign participants as a custom field or linked activity log.

Aurea Partner relationship management records (partner leads, quota assignments, territory assignments, partner status) do not have a direct Pipedrive equivalent. We map partner records to Pipedrive Organizations with a custom field partner_status__c (active, inactive, prospect) and partner_type__c (reseller, referral, distributor) to preserve the partner classification. Partner-specific quota and territory data is captured as custom fields on the Organization record. The customer's admin decides whether to expose these as filterable fields in Pipedrive's pipeline views.

Aurea document management stores files linked to Contact, Account, and Opportunity records. We migrate document references as attachment links where the Aurea file store is accessible, or we flag records with high attachment volume for manual migration review. Pipedrive's file attachment API accepts uploads linked to Person, Organization, Deal, or Activity records. Binary files (PDFs, images) upload directly to Pipedrive; links to inaccessible external file stores are documented in the migration report as items requiring manual re-attachment.

Aurea administrator-defined custom fields across all objects (Contact, Account, Opportunity, Activity) are cataloged during discovery and mapped to Pipedrive custom fields. We preserve field data types where possible: Aurea text fields map to Pipedrive text fields, picklist fields map to Pipedrive select or multi-select fields, date fields map to Pipedrive date fields, and numeric fields map to Pipedrive numeric fields. Complex picklist dependencies or multi-field conditional logic from Aurea CRM.designer are documented for manual configuration in Pipedrive.

Aurea User records migrate as Pipedrive User accounts. We match by email address to identify existing Pipedrive users or flag records for new user provisioning. Active Aurea users map to active Pipedrive users; inactive Aurea users map to inactive Pipedrive users to preserve assignment history on historical records. Owner assignment on Contact, Account, Opportunity, and Activity records migrates by resolving the Aurea user email to the Pipedrive User id at migration time.

Aurea Territory and Quota data (territory assignments, sales quota values, and quota periods) does not have a native Pipedrive equivalent object. We migrate territory assignments as a custom select field on the Pipedrive User record (territory__c) and quota values as a custom numeric field (quota_amount__c). The customer's admin can use Pipedrive's Goals feature or a custom report to track quota attainment against the imported values. This approach does not replicate Aurea's territory-based routing, which requires a separate Pipedrive automation or admin configuration.