Migrate from Opal CRM to HubSpot

Opal Leads map directly to HubSpot Contacts. The HubSpot lifecycle_stage property is set to 'lead' for all migrated records. Original create dates are preserved in a custom datetime property (e.g., Original_Create_Date__c) for historical reporting continuity. Owner resolution happens via email address matching against existing HubSpot user accounts. Unmatched owners are flagged before migration for team invite or fallback assignment.

Opal Contacts migrate to HubSpot Contacts in a 1:1 relationship. Name, email address, phone number, job title, physical address, and company association all map directly to HubSpot standard properties. Opal's primary company association maps to the HubSpot contact's associatedcompanyid field. Any secondary Opal company associations are preserved as association notes or custom properties for post-migration review.

Opal Company records map to HubSpot Company records. Company name, domain, industry classification, employee count, and annual revenue all map directly. Opal's parent-company hierarchy maps to HubSpot's parent Company ID field. Organizations with multi-branch structures may require post-migration grouping via custom properties or manual tagging since HubSpot's company hierarchy model differs from Opal's approach.

Opal Deals migrate to HubSpot Deals with deal name, amount, close date, owner, and stage preserved. Each Opal pipeline becomes a separate HubSpot pipeline. Pipeline stage names map value-by-value to HubSpot stage names within each pipeline. Stage probabilities are re-applied according to HubSpot's stage configuration interface. Deal-contact associations and deal-company associations resolve via email lookup.

Opal Quotation objects with header metadata and line items transform into HubSpot Products and Line Items linked to the migrated Deal. Each quotation line becomes a Line Item referencing a Product record. If an Opal quotation references a product that does not exist in HubSpot, FlitStack creates a placeholder Product record and flags it for your admin to populate pricing and details after migration.

Opal call logs migrate as HubSpot engagements with Type='Call', original timestamp, call duration, call direction (inbound/outbound), and owner preserved. Each call is associated to the migrated contact record via HubSpot's engagement association API. Dispositions or outcome notes from Opal map to HubSpot engagement metadata fields or custom properties on the associated contact record.

Opal email activity migrates as HubSpot email engagements. Subject line, body content, timestamp, and owner are all preserved during migration. Associations link each email to the migrated contact and company records. Plain-text emails migrate cleanly; rich-text emails are re-rendered in HubSpot's engagement format using its internal HTML rendering pipeline.

Opal meeting records migrate as HubSpot engagements with Type='Meeting'. Start time, end time, meeting location, title, and assigned owner all transfer to HubSpot's engagement properties. Meeting attendees are resolved by email address against migrated HubSpot contacts to maintain association integrity. Original create timestamp is preserved for historical reporting continuity and audit trail purposes.

Opal notes migrate as HubSpot Notes on the associated contact or company record. Note body text, create date, and owner are preserved during the migration. Notes attached to deals link to the migrated HubSpot Deal via deal-association labels. Notes without a parent record are attached to the most relevant contact by email lookup and owner resolution.

Opal owner records are resolved by email address against HubSpot user accounts. Matched owners map directly to their corresponding HubSpot user. Unmatched owners are flagged before migration so your team can invite them to HubSpot or assign records to a fallback owner. No record lands in HubSpot without an owner assignment; the audit log tracks all ownership resolutions.

Opal custom fields on any object map to HubSpot custom properties. Data type is matched — text, number, date, pick-list, checkbox — and the HubSpot property is created in your account before migration runs. Pick-list custom fields require value-by-value mapping if the available options differ between Opal and HubSpot.

Opal file attachments on records re-upload to HubSpot Files and are re-associated to the migrated record. Files are downloaded from Opal's storage and uploaded to HubSpot's file management. HubSpot's 25MB per-file limit is enforced; files exceeding this are flagged for splitting or alternative handling.