Migrate from PlanPlus Online to HubSpot

PlanPlus contacts migrate directly to HubSpot contacts. The contact's primary associated company in PlanPlus links to the corresponding HubSpot company record via the company_id association. If no company is associated, the contact lands standalone with no company link.

PlanPlus company records map 1:1 to HubSpot company records. Company domain in PlanPlus maps to the HubSpot company domain property. PlanPlus parent-child company hierarchies preserve using HubSpot's parent company association field if the structure exists.

PlanPlus opportunities become HubSpot deals. The opportunity name becomes the deal name, amount transfers directly, and close date maps to the HubSpot deal close date. The PlanPlus opportunity stage maps to a HubSpot deal pipeline stage via a value-mapping table you define before migration.

PlanPlus does not have named multi-stage pipelines by default — opportunities are single-stage records. If your PlanPlus account uses a pipeline metaphor (e.g., 'Sales Pipeline' with stages), we create a corresponding HubSpot deal pipeline with your specified stage names. Without a named pipeline in PlanPlus, we create a default HubSpot pipeline and map opportunity statuses to stages.

PlanPlus Online has no native lifecycle stage equivalent. All migrated contacts land with lifecycle_stage = 'subscriber' by default. If your PlanPlus data contains lead status or contact type fields, we use those values to set more granular HubSpot lifecycle stages (lead, MQL, etc.) per your mapping specification.

PlanPlus tasks migrate as HubSpot engagements with type='task'. Task subject maps to the engagement title, due date preserves, completion status transfers, and the associated contact or deal links via HubSpot's association API. Completed tasks appear with their completion timestamp in HubSpot's activity timeline.

PlanPlus calendar events migrate as HubSpot meetings. Event title, start time, end time, and location transfer directly. Attendees resolve to HubSpot contacts by email match — any attendee without a matching HubSpot contact is logged as a notes attachment on the associated record.

PlanPlus notes migrate as HubSpot engagements with type='note'. The note body text transfers, timestamp preserves, and the note associates to the parent contact or company record. Rich-text formatting in PlanPlus notes converts to plain text for HubSpot compatibility.

PlanPlus contact-level custom fields create HubSpot custom contact properties. HubSpot does not use the __c suffix — custom properties appear in the property list under Settings → Properties. We create the property in HubSpot before migration and map the field name (with spaces converted to underscores) to the property internal name.

PlanPlus company custom fields map to HubSpot company custom properties following the same naming convention. For pick-list or multi-select fields in PlanPlus, we create matching pick-list properties in HubSpot and apply value-by-value mapping if the option labels differ between platforms.

PlanPlus user records resolve to HubSpot users by email match. The owner_id on each PlanPlus record (contact, company, opportunity) maps to the HubSpot user who owns the record post-migration. Unmatched owners flagged before migration — your team either creates HubSpot users first or assigns records to a fallback HubSpot owner.

PlanPlus file attachments associated with contacts, companies, or opportunities download and re-upload to HubSpot Files. File size limits apply (HubSpot default 25MB per file). We preserve the attachment association by linking the uploaded file to the same HubSpot record after upload.

PlanPlus workflow definitions and email sequences do not have a migration path. We export a JSON representation of your PlanPlus workflow rules (trigger conditions, action sequences, timing) as a rebuild reference. Your HubSpot admin uses this document to reconstruct equivalent workflows in HubSpot's Workflows tool.