Migrate from Populate to HubSpot

Direct map. HubSpot contacts are property-bags: every attribute from the source contact maps as a named HubSpot property on the contact record. The source contact's primary company association maps to a HubSpot company association using HubSpot's association API. Contacts without a primary company in the source land in HubSpot without a company association and can be linked later.

Direct map. HubSpot companies store name, domain, industry, employee count, annual revenue, and address as native properties. Source parent-child company hierarchies map to HubSpot's parent company association. Multi-company contacts collapse to a single primary company association in HubSpot, with additional associations surfaced as secondary links.

Direct map. HubSpot deals carry deal name, amount, close date, pipeline, stage, and owner as native properties. Source deal custom properties map as HubSpot deal properties. Each deal links to a HubSpot pipeline object whose stage pick-list values are scoped to that pipeline only, matching the source pipeline's stage set.

Direct map. HubSpot pipelines are native objects separate from deals. Each source deal pipeline becomes one HubSpot pipeline. The source pipeline's stage names and order map to HubSpot pipeline stage names in the same sequence. Stage probability values from the source are preserved as metadata for reporting continuity.

Direct map. Source call records migrate as HubSpot engagement records with type 'Call.' The call subject, duration, direction (inbound/outbound), outcome, and original timestamp migrate to HubSpot engagement properties. The call is linked to the associated contact ID so it appears in the contact's timeline.

Direct map. Source email engagement records migrate as HubSpot engagement records with type 'Email.' The email subject, body text, and original timestamp migrate to HubSpot engagement properties. Attachments referenced in the source email are re-uploaded as HubSpot Files and linked to the engagement record.

Direct map. Source meeting records migrate as HubSpot engagement records with type 'Meeting.' The meeting title, start time, end time, location, and associated contacts map to HubSpot engagement properties. The original timestamp and owner are preserved so the meeting appears in the contact and company timeline at the correct date.

Direct map. Source note records migrate as HubSpot notes on the associated contact or company. The note body text, creation timestamp, and owner are preserved. If the source note is associated with multiple records, FlitStack creates a primary note on the contact and attaches it to additional records via HubSpot's association API.

Direct map. Source owner records resolve to HubSpot owners by email address match. Owner name, email, and HubSpot owner ID are mapped so all records in HubSpot carry the correct owner. Source owners without a matching HubSpot user email are flagged before migration so the team can either invite them to HubSpot or reassign their records.

Direct map on HubSpot Enterprise. Source custom objects migrate to HubSpot custom objects 1:1. Custom object associations that use a many-to-many relationship in the source require HubSpot junction objects — FlitStack surfaces this in the migration plan so the HubSpot admin can pre-create the junction object schema before data lands.

Direct map. Source file attachments on contacts, companies, and deals are downloaded and re-uploaded as HubSpot Files, then linked to the associated CRM record. Files larger than HubSpot's 25 MB per-file limit are flagged for manual handling. Inline images embedded in notes are extracted, rehosted as HubSpot Files, and the image URLs are updated in the note body.

No direct migration. Workflows and sequences are automation logic stored in the source system, not data attached to records. HubSpot has no native equivalent for sequences. FlitStack exports the source workflow definitions as a structured reference document and shares it with the team so the HubSpot admin can rebuild the logic in HubSpot's Workflows tool.

Roles, permissions, and sharing rules are destination‑side access‑control configuration that has no direct migration path. HubSpot models access using Teams, Roles, and individual user permissions, which must be configured separately after data lands. FlitStack exports a permission inventory from the source — listing each role, its associated users, and any sharing rules — so the HubSpot admin can recreate the same access hierarchy in HubSpot's access‑control settings.

Third-party integrations and connected apps are connection credentials scoped to the source platform, not transferable data. Each integration must be rebuilt in HubSpot using HubSpot's app marketplace connectors, private apps, or custom API integrations. The source integration list serves as an inventory for the rebuild plan, and FlitStack can provide a checklist of required scopes and callback URLs for each integration.

Reports and dashboards are source-platform configuration, not data. HubSpot's report builder uses HubSpot-native objects and properties, so source reports cannot be imported directly. The underlying data migrates; the report and dashboard definitions must be rebuilt in HubSpot's analytics tools.

Custom object associations that use a many-to-many relationship in the source require HubSpot junction objects. FlitStack surfaces this in the migration plan so the HubSpot admin can pre-create the junction object schema before data lands.

Source custom fields that have no direct HubSpot equivalent are preserved as custom properties in HubSpot. The team decides on naming, type, and pick-list options before migration so FlitStack can create the properties and map values correctly.