Migrate from Aurea CRM to HubSpot

Aurea CRM contacts map 1:1 to HubSpot contacts. The migration applies the contact's primary-company rule (most-recently-modified company becomes HubSpot's associated-company). All Aurea extended properties become HubSpot custom properties; the Aurea contact status or custom stage field maps to HubSpot's lifecycle_stage picklist value. Original create and update timestamps are preserved in FlitStack custom fields (hs_createdate is set at migration time).

Aurea CRM companies map 1:1 to HubSpot companies. Aurea company hierarchies (parent-company links) translate to HubSpot's Parent Company association; circular references are flagged before migration. Industry picklist values are mapped via a value-mapping table against HubSpot's standard Industry picklist — unmapped values land as custom text in a separate custom property.

Aurea CRM opportunities map to HubSpot deals with deal name, amount, close date, and owner preserved. If Aurea uses named deal stages, those stage names map via value-mapping to HubSpot deal pipeline stages. Aurea's deal priority (or custom urgency field) becomes a HubSpot custom property since HubSpot does not have a native priority field on deals.

Aurea CRM's pipeline structure (if named and ordered) maps to a HubSpot deal pipeline. If Aurea does not use named pipelines, FlitStack creates a single HubSpot deal pipeline named 'Default' and maps all Aurea opportunities into it. Each Aurea opportunity stage maps to a HubSpot deal stage via the Pipelines API, with probability values assigned per stage.

Aurea CRM call records (subject, call duration, disposition, notes) map to HubSpot call engagement records via the Engagements API. The Aurea call title populates hs_call_title; call duration in seconds becomes the HubSpot call duration field. Owner email resolves to the HubSpot owner ID; unresolved owners receive a FlitStack flag before the migration runs.

Aurea CRM email logs (subject, body, timestamp, from/to addresses) map to HubSpot email engagement records. The email subject becomes the engagement title; body content is preserved as HTML text. Emails are linked to the parent Aurea contact record by email address — FlitStack resolves contacts by email before writing the engagement association.

Aurea CRM meeting records (title, start time, end time, location, notes) map to HubSpot meetings via the Meetings API. The meeting title populates hs_meeting_title; original start/end times and duration are preserved. Meeting associations link to the Aurea contact record that owns the meeting.

Aurea CRM notes (title, body, associated contact or company) map to HubSpot notes via the CRM Notes API. The Aurea note title becomes hs_note_title; note body populates hs_note_body. Notes are associated by email lookup to the HubSpot contact or by domain match to the HubSpot company.

Aurea CRM file attachments linked to contacts, companies, or opportunities are downloaded and re-uploaded to HubSpot Files. File size limits apply (HubSpot default 25 MB per file; larger files are chunked). Inline images embedded in Aurea notes are extracted, saved as separate image files, and re-embedded in the corresponding HubSpot note body.

Aurea CRM extended contact properties that have no HubSpot standard-field equivalent are created as HubSpot custom properties (string, number, date, or picklist matching the Aurea field type). For Aurea picklist fields, FlitStack creates a HubSpot picklist with the Aurea values and applies value-by-value mapping. Property names are normalized to camelCase.

Aurea CRM extended company properties become HubSpot company custom properties following the same type-matching and naming conventions as contact custom properties. Aurea company-specific property groups are iterated per company record during the migration load. The mapping plan documents each property's HubSpot type and any required value transformations before loading.

Aurea CRM opportunity custom fields map to HubSpot deal custom properties. Long-text Aurea fields (e.g., deal description, internal notes) become HubSpot multi-line-text custom properties. Date fields use HubSpot date type; numeric fields use HubSpot number type. The mapping plan records each custom field's source name and the corresponding HubSpot property identifier for reference.

Aurea CRM workflows have no direct HubSpot equivalent and cannot be migrated. FlitStack exports Aurea workflow definitions as structured JSON (trigger type, conditions, actions per step). HubSpot admins use this export as a reference document to rebuild equivalent automations in HubSpot's Workflows tool or ActiveLists. Data-only migration proceeds independently of automation rebuild.

Aurea CRM's N:N contact-company model allows a contact to have multiple unrelated company associations. HubSpot enforces one primary company per contact. FlitStack resolves the most-recently-modified Aurea company link as HubSpot's primary company and surfaces the remaining Aurea companies as additional association labels. Teams that need full N:N parity create a custom junction object post-migration.