Migrate from Aurea CRM to Twenty CRM

Aurea CRM Contact records map 1:1 to Twenty CRM Person records. Standard contact fields (name, email, phone, address, role) migrate directly. The Aurea Contact-to-Account relationship (which Contact belongs to which Company Info Area record) is preserved as a Company lookup on the Person record in Twenty. We resolve the parent Company reference during extraction and insert Person records after Company records are loaded to satisfy the lookup dependency.

Aurea Company Info Area records map to Twenty CRM Company records. Company name, industry, website, address, and annual revenue fields migrate directly. We extract all active Company records before Contact extraction so that the Person-to-Company relationship is valid at import time. Dedupe is performed on Company name and domain where available.

Aurea Opportunity records map to Twenty CRM Opportunity records. Deal value, stage name, close date, probability, and owner assignment migrate directly. Aurea's pipeline stage labels are configurable per installation and must be mapped explicitly to Twenty's Opportunity stage values during discovery. Closed-won and closed-lost reasons from Aurea custom fields migrate as Opportunity custom fields in Twenty.

Aurea Task records (a subtype of Activity) map to Twenty Activity records with type set to Task. Subject, description, due date, status, and priority migrate. Owner assignment is resolved by matching Aurea user IDs to Twenty user emails. Legacy activity subtypes in Aurea that do not map cleanly to standard CRM activity types are flagged during discovery and mapped to the nearest Twenty Activity type with a note on the record.

Aurea Call records map to Twenty Activity records with type set to Call. Call disposition, duration, and outcome fields migrate to custom Activity fields in Twenty. Timestamps (created_at, completed_at) are preserved from the Aurea export to maintain the activity timeline sequence in Twenty.

Aurea Email activity records map to Twenty Activity records with type set to Email. Email subject, body, sender, and recipient fields migrate to Twenty Activity fields. If the Aurea export captures email thread references, these are stored as custom fields for context. Email attachments in Aurea migrate as file attachments on the Activity record.

Aurea Meeting records map to Twenty Activity records with type set to Meeting. Meeting title, start and end time, location, and attendees migrate. Attendee names are linked to Twenty Person or Company records where matches exist; unmatched attendees are stored as free-text participant records on the Activity.

Aurea Campaign Manager records include campaign name, type, status, and response metrics. These map to Twenty CRM, though Aurea-specific campaign workflow logic does not transfer. Campaign records with revenue attribution map to Opportunities linked to the campaign; campaigns without direct revenue attribution are stored as Twenty CRM custom records or linked to a Company as a source attribution field. The customer decides during scoping whether to migrate campaigns as a standalone object or collapse them into opportunity attribution.

Aurea Partner relationship management records track channel partners with partner-specific quota and territory assignments. We map partner records to Twenty Person records with a partner_role custom field set to Partner. Quota and territory data from Aurea's PRM module migrates to custom fields on the Person record, though the territory assignment model differs from Twenty's standard organization model and may require post-migration admin review.

Aurea CRM document management stores files linked to records. We migrate documents as attachment references where the file store is accessible via the Aurea export. If the document store is not reachable, we flag records with high attachment volume for manual handling and provide a documented list. File migration depends on export format availability confirmed during scoping; PDF and image attachments are handled differently from structured data exports.

Aurea CRM custom fields across all Info Areas are catalogued during discovery and created in Twenty's Settings → Data Model before any data import begins. This is a prerequisite for CSV import in Twenty, which creates records but not fields. Complex Aurea picklist fields (multi-select, conditional picklists) require explicit mapping to Twenty's custom field types during discovery. We flag any Aurea field types with no direct Twenty equivalent for customer decision during scoping.

Aurea User and Owner records map to Twenty CRM User accounts. We extract all distinct Aurea user IDs and emails referenced on Contact, Account, Opportunity, and Activity records and match them against Twenty user accounts. Owners without a matching Twenty user are held in a reconciliation queue for the customer's admin to provision before record import resumes. Active versus inactive status is preserved based on the Aurea user account state at extraction time.