Migrate from PipelineManager to HubSpot

PipelineManager People map 1:1 to HubSpot Contacts. FlitStack resolves each Person's owner by email match against HubSpot users. Multi-phone fields (array type in PipelineManager) require transformation to HubSpot's Phone + Mobile Phone structure — we pick the first value as primary and surface additional values as a custom field.

PipelineManager Organizations map one‑to‑one to HubSpot Companies, including name, domain, website, address, industry, and employee count. Parent‑child hierarchies in PipelineManager translate to HubSpot's Parent Company lookup, preserving organizational structure. For Organizations that have no linked People, FlitStack creates placeholder Companies marked for review, ensuring orphaned organizations appear in the reconciliation report for your team to validate.

PipelineManager's N:N person-organization model allows one Person to belong to multiple Organizations. HubSpot supports this via a primary Company lookup on Contact plus Account Contact Relationships for secondary associations. We migrate the most-recently-modified Organization as primary and create Account Contact Relationships for the rest.

PipelineManager Deals migrate one‑to‑one to HubSpot Deals, preserving the Deal name, amount, currency, expected close date, owner, and all custom properties. Stage names map to HubSpot Deal Stage values through a value‑by‑value lookup, with probabilities and forecast categories applied from HubSpot's stage configuration. PipelineManager's stage‑entered timestamps are stored as custom datetime fields (Stage_Entered_Date__c) because HubSpot natively records only the current stage, not transition history.

PipelineManager supports multiple People linked to a single Deal, allowing roles such as champion, economic buyer, or technical evaluator. HubSpot's Deal Contact Associations replicate this relationship, and FlitStack maps each PipelineManager person‑deal link to a corresponding HubSpot association, preserving the role context when a role label exists in PipelineManager. The migration ensures all associated contacts appear in the Deal's timeline and that deal‑level activity associations remain intact after cutover.

PipelineManager's Pipeline is a container object that does not exist in HubSpot's data model. HubSpot models pipelines implicitly via Deal Stage pick-lists. We create a Pipeline_Name__c custom property on Deals to preserve which PipelineManager pipeline each deal originated from, enabling reporting continuity.

PipelineManager stage names map to HubSpot Deal Stage values via a value‑by‑value translation, keeping each label intact. Probabilities and forecast categories are applied per HubSpot's stage configuration, preserving expected win‑rate logic. Stage sequence order is maintained, and PipelineManager stage‑entered timestamps are stored as custom datetime fields on the Deal (e.g., Stage_Entered_Date__c) to retain historical progression that HubSpot does not natively track.

PipelineManager activity records map to their HubSpot equivalents by type. PipelineManager may merge sequential emails or calls into a single thread — we flatten these into individual HubSpot activity records with original timestamps to preserve the full audit trail. Owner and associated Contact/Deal links are maintained.

PipelineManager custom fields on People, Organizations, and Deals map to HubSpot custom properties. Field type compatibility is validated — text, number, date, and pick-list fields map directly. Array-type fields (e.g., multiple values in one field) are decomposed into separate HubSpot custom fields or concatenated into a text field per the client's preference.

PipelineManager files attached to People, Organizations, and Deals are re-uploaded to HubSpot Files and linked to the corresponding record. File metadata (original filename, upload date, file size) is preserved. Files exceeding HubSpot's 25MB per-file limit are flagged for chunked re-upload or alternative hosting with a reference link.

PipelineManager users are matched to HubSpot users by email address. Unmatched users are flagged before migration — your team can invite them to HubSpot first or assign their records to a fallback owner. PipelineManager user roles and permissions do not migrate as they are destination-side configuration.