Migrate from Results to HubSpot

Results contacts map directly to HubSpot contacts. Because HubSpot requires a lifecycle_stage property on every contact, FlitStack creates a custom lifecycle_stage property and populates it using the contact status from Results, or a custom status field if present. Original create dates and owner assignments are preserved in custom properties to maintain historical context after migration.

Results companies are mapped to HubSpot companies, preserving fields such as domain, industry, and employee count that map natively to HubSpot properties. Parent‑company relationships in Results translate to HubSpot’s parent company association using the parent_company_id property, ensuring hierarchical data is retained. Any additional company fields that lack a direct HubSpot counterpart are created as custom properties before import.

Results deals map to HubSpot deals, with each deal pipeline in Results becoming a separate HubSpot pipeline object. Deal stage names are translated to HubSpot stage values through value‑by‑value mapping configured during the mapping phase, preserving the original sales progression. Deal amount, close date, owner, and any custom fields are transferred to matching HubSpot properties.

Results pipelines translate to HubSpot pipeline objects. In Results, pipelines define deal stage order and names. In HubSpot, pipelines are created in the pipeline settings UI and referenced by deal records via the pipeline property. FlitStack creates HubSpot pipelines matching Results pipeline definitions.

Results custom fields that have no direct HubSpot equivalent require HubSpot custom property creation before migration. FlitStack creates each custom property in HubSpot with the matching type (text, number, date, picklist, checkbox) so import validation succeeds on the first pass.

Results owner references map to HubSpot users by email address. FlitStack queries HubSpot users by email and creates a lookup map. Any Results owner whose email does not match a HubSpot user is flagged before migration so the team can invite them or reassign records.

Results file attachments are downloaded by FlitStack and re‑uploaded to HubSpot Files, then attached to the corresponding contact, company, or deal record. File size limits enforced by HubSpot apply, and any attachments that cannot be retrieved due to expired URLs or permission issues are flagged for manual recovery before the migration commits. Original file names, sizes, and upload timestamps are preserved in HubSpot’s file metadata.

Results engagement records—including calls, emails, meetings, and notes—are migrated to HubSpot engagements with original timestamps and owner information preserved. Each type of engagement in Results maps to the corresponding HubSpot engagement type in the timeline model, ensuring that activity history remains intact. Attachments linked to engagements are transferred as HubSpot Files and attached to the relevant engagement record.

Results custom objects map to HubSpot custom objects if the source uses HubSpot-compatible custom object types. HubSpot Enterprise allows custom object creation. N:N associations in Results that cannot map to HubSpot's built-in association model are preserved using a custom association property.

Results internal record IDs are stored as a custom property (Source_System_ID__c) on each HubSpot record to enable traceability, support delta‑run de‑duplication, and allow cross‑referencing between Results and HubSpot after cutover. This property also facilitates reconciliation by linking historical data in HubSpot back to the original Records entries, maintaining data integrity throughout the migration lifecycle.