Migrate from Factoreal to HubSpot

Direct 1:1 map. HubSpot Contact properties receive Factoreal contact fields verbatim. Owner resolution happens by email match against HubSpot users. Unmatched owners are flagged before migration so your team can invite them to HubSpot or assign a fallback owner. All original create dates and engagement timestamps are preserved as custom properties to maintain historical reporting continuity.

Direct 1:1 map. Factoreal company records become HubSpot company records. Address fields, domain/website, industry, and employee count map to HubSpot company properties. Parent-company relationships in Factoreal map to HubSpot's parent company association. All address components (city, state, country, zip) are transferred verbatim, and any custom fields on the company object are migrated as HubSpot custom properties.

Direct 1:1 map where Factoreal tracks standalone deals. Amount, stage, close date, owner, and deal name transfer as HubSpot deal properties. Deals without a standalone deal object in Factoreal (campaign-tracked deals) require a pre-migration audit to identify and create the appropriate HubSpot deal records.

Factoreal campaigns (email, SMS, WhatsApp) map to HubSpot CRM Campaigns for email and to a custom multi-select property on Contact for multi-channel tracking. HubSpot has no unified multi-channel campaign object — we surface this in the migration plan and you decide whether to use separate HubSpot tools per channel or collapse into a single reference property.

Factoreal email engagement events (opens, clicks, replies) become HubSpot contact timeline entries of type 'email'. Original engagement timestamps and campaign attribution are preserved as custom properties on the timeline entry so reporting reflects the source campaign. If a contact has multiple engagements for the same campaign, each event is recorded as a separate timeline entry to preserve the full activity history.

SMS and WhatsApp engagement events in Factoreal map to HubSpot custom engagement types on the contact timeline. HubSpot's native tools for SMS and WhatsApp (Conversations Inbox, WhatsApp integration) are separate from the CRM timeline — we write engagement history as reference entries and your team connects the native channels post-migration.

Factoreal custom contact properties migrate as HubSpot contact properties. Property type is preserved (text, number, date, picklist) where possible. Multi-select pick-lists in Factoreal map to HubSpot multi-checkbox properties. Date fields map to HubSpot date properties with original values intact. Any properties that cannot map directly are flagged and discussed with your team for custom conversion logic.

Factoreal custom company properties migrate as HubSpot company properties using the same type-preservation logic as contact properties. Industry and employee-count fields map to HubSpot's standard company properties when the values match HubSpot's pick-list formats. Custom fields that do not fit HubSpot's property types are logged for manual review and potential custom‑property creation.

Factoreal custom deal properties migrate as HubSpot deal properties. Amount, probability, and stage-related fields require value mapping if Factoreal uses different stage names than HubSpot's default deal pipeline stages. We also transfer any custom deal-level notes, attachments, or activity logs as HubSpot deal properties to preserve full context.

Factoreal users are matched to HubSpot users by email address. Active Factoreal users who do not yet have HubSpot accounts are flagged in the migration plan — your team creates the HubSpot users before migration runs so all records land with an assigned owner.

Contact-to-campaign associations in Factoreal are critical for reporting continuity. We preserve these as a custom multi-select text property on each contact listing the Factoreal campaigns they were enrolled in. HubSpot's native CRM Campaigns can be populated for email campaigns if your team chooses to rebuild the campaign structure in HubSpot.