Migrate from Pipeline CRM to HubSpot

Pipeline CRM Person maps to HubSpot Contact as a direct object-level map. All standard person fields (name, email, phone, address) become HubSpot contact properties. Custom fields on the Person record become HubSpot contact properties — all must be pre-created in HubSpot before migration runs so the import can write values to them.

Pipeline CRM Company maps to HubSpot Company directly. Company name becomes Company Name, domain becomes Website, industry and employee count map to the equivalent HubSpot properties. Parent-child company hierarchies in Pipeline CRM use the same parent_company_id field and map to HubSpot's parent_company_id property, preserving the hierarchy in HubSpot's company associations.

Pipeline CRM Deal maps to HubSpot Deal directly. Deal name, amount, close date, and stage all have direct HubSpot equivalents. The pipeline association in Pipeline CRM becomes HubSpot's pipeline_id — each Pipeline CRM pipeline must map to a corresponding HubSpot pipeline created before the migration runs. Stage order is preserved via HubSpot's displayOrder metadata.

Every Pipeline CRM custom field on Person, Company, or Deal becomes a HubSpot property. Field types in Pipeline CRM (text, number, date, dropdown, checkbox) map to HubSpot property types — dropdown fields in Pipeline CRM become HubSpot select/multi-select properties and require value-by-value mapping if pick-list values differ from HubSpot's defaults. All custom properties must exist in HubSpot before the migration imports data into them.

Pipeline CRM Activities map to HubSpot engagement records. The activity type field in Pipeline CRM (task, call, email, meeting, note) determines the HubSpot engagement type — tasks become HubSpot tasks, calls become call engagements, meetings become meeting engagements, and notes become HubSpot note engagements with the original timestamp preserved. Activities are linked to their parent record (person, company, or deal) via HubSpot's association API.

Each Pipeline CRM pipeline becomes a HubSpot pipeline. Each stage within the pipeline becomes a HubSpot deal stage with the same label and displayOrder preserved. A key difference: Pipeline CRM stages may not have probability values configured, but HubSpot requires probability metadata per stage for its forecasting model to function — we assign the standard 0.1–1.0 probability band per stage position unless source data provides explicit values.

Pipeline CRM owner_id on Person and Deal records maps to HubSpot owner_id. Resolution happens by matching the Pipeline CRM owner email to a HubSpot user by email address. Unmatched owners are flagged before migration commits — teams either invite them to HubSpot first or assign records to a fallback owner. This prevents records from landing without a valid HubSpot owner.

Company owner in Pipeline CRM follows the same email-match resolution as Person and Deal owners. We resolve against HubSpot users by email and flag any Pipeline CRM owners who do not have a corresponding HubSpot account. A fallback owner assignment is applied to unresolved records unless the team specifies a different rule before migration runs.

Pipeline CRM automation rules have no equivalent in HubSpot — they cannot be migrated as data records. FlitStack AI exports the rule definitions (trigger type, conditions, actions) as a structured JSON reference file that your HubSpot admin can use to rebuild equivalent workflows in HubSpot's workflow builder. This export does not transfer automatically; it is a rebuild reference only.

File attachments on Pipeline CRM People, Companies, and Deals are downloaded and re-uploaded to HubSpot Files. Each file is associated to its parent record via HubSpot's file association API. Files that exceed HubSpot's size limits (default 25MB per file) are flagged for manual handling before the migration runs. Inline images embedded in notes are extracted and uploaded as separate file records.