Migrate from Omni.us to HubSpot

Omni.us contacts map 1:1 to HubSpot contacts. Email, name, phone, job title, and address fields translate directly. Omni.us owner ID resolves to HubSpot user by email match; unassigned contacts land under a default owner flagged for review. Original create and update timestamps are preserved as custom datetime fields in HubSpot.

Omni.us companies map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue map directly. Parent-company hierarchies in Omni.us translate to HubSpot's parent company field using ID-based linking. Industry pick-list values require value mapping to HubSpot's standard industry list.

Omni.us deals map to HubSpot deals with amount, close date, and stage preserved as direct field mappings. Deal name becomes dealname in HubSpot. Owner resolution happens by email match to HubSpot users before deal creation. The Omni.us deal ID is stored in a custom property for traceability and de-duplication.

Omni.us deal stages map to HubSpot pipeline stages. Each Omni.us deal type or category creates a corresponding HubSpot pipeline with its own stage set. Stage order and names are preserved during migration; probability values are configurable post-migration in HubSpot's pipeline settings. Multiple deal types from Omni.us result in multiple HubSpot pipelines.

Omni.us call, email, and meeting activities become HubSpot engagements with original timestamps, owner attribution, and parent-record association preserved. Activity type (call, email, meeting) maps to HubSpot engagement type (CALL, EMAIL, MEETING). FlitStack normalizes timestamps to UTC during the transform step before importing to HubSpot.

Omni.us notes migrate to HubSpot notes with body content and original create timestamps preserved. Notes associate to the parent record (contact, company, or deal) by Omni.us record linkage using HubSpot's association API. Rich-text formatting is preserved where Omni.us supports it; inline images are extracted and rehosted as HubSpot-hosted files.

Omni.us custom fields on contacts, companies, and deals create HubSpot custom properties via the HubSpot Properties API. Field type parity determines mapping: text maps to string, number maps to number, date maps to datetime. Custom properties require HubSpot Operations Hub on Starter and Professional tiers to create beyond the default limit.

Omni.us pick-list fields map to HubSpot drop-down custom properties with value-by-value translation. Pick-list option labels are preserved verbatim during migration. Option values must be pre-created in HubSpot's property settings before the migration run; order may be reconfigured post-migration in HubSpot's UI.

Omni.us contact-to-company and contact-to-deal association labels migrate as HubSpot association labels using the Associations API. Decision-maker, influencer, and other role labels transfer directly. HubSpot supports labeled associations on the Contact, Company, and Deal records with multiple label types per association.

Omni.us file attachments download and re-upload to HubSpot Files using the Files API, attached to the corresponding record (contact, company, or deal) via the associations API. File size limits apply per HubSpot tier (100MB Starter, 10GB Professional, 25GB Enterprise). Inline images in notes are extracted and rehosted as HubSpot-hosted files.

Omni.us owner records resolve to HubSpot users by email address match using the HubSpot Users API. If a HubSpot user account does not exist for an Omni.us owner, the owner is flagged in the migration audit and records are assigned to a fallback owner designated before migration runs.

Omni.us internal record IDs are stored in HubSpot custom properties (Source_System_ID__c) for traceability and delta-run de-duplication. Original create and update timestamps from Omni.us are preserved as custom datetime fields (Original_Create_Date__c, Original_Update_Date__c) since HubSpot's native timestamps reflect migration time.