Migrate from Wired Plus to HubSpot

Wired plus contact records map 1:1 to hubspot contacts. All standard fields — name, email, phone, job title, address — migrate directly. The migration assigns hubspot lifecycle_stage values post-import based on deal history and engagement patterns since wired plus stores no lifecycle data.

Wired plus company records migrate to hubspot companies. Domain and website map directly. Hubspot company properties like industry and employee count receive wired-plus field values where available — gaps are left blank for manual enrichment post-migration. Company type and phone number also migrate directly when present in the wired-plus record.

Wired plus deals map to hubspot deals with the wired-plus pipeline becoming a hubspot pipeline in the destination crm. Deal name, amount, close date, and owner migrate directly. Pipeline-stage values require value-by-value mapping to hubspot stage names. Associated contact links are resolved during the deal import phase.

Each wired-plus pipeline stage name maps to a corresponding hubspot deal stage. Probability weights and forecast categories are re-applied based on hubspot's stage-configuration model. The stage sequence order is preserved from wired plus.

Wired plus call logs, email activities, and meeting records migrate as hubspot engagements with original timestamps and owners preserved. Call duration stored in wired plus as seconds converts to hubspot's duration format on the engagement record. Email subjects and body content migrate as engagement subject and body fields.

Wired plus notes migrate to hubspot notes attached to the parent contact or company record. File attachments are downloaded and re-uploaded to hubspot file storage. File size limits are enforced — hubspot allows 25MB per file. Notes retain their original created timestamps where available.

Wired plus custom fields on contacts and companies are created as hubspot custom properties. Field types are translated: text stays text, number stays number, date fields convert to hubspot date format, and multi-select values are mapped to hubspot multi-checkbox property types. The original property names are preserved for reporting continuity.

Wired plus users are resolved by email match against hubspot users. Owners without a matching hubspot email are flagged pre-migration — teams either invite them to hubspot first or assign records to a fallback owner before the full run commits.

Wired plus stores campaign attribution and source tracking as custom contact properties. These migrate as hubspot contact properties for segmentation and reporting continuity. The original property names are preserved to maintain reporting consistency across the platform transition.

Wired plus contact-to-company associations migrate as hubspot primary company associations on contacts. Wired plus deal-to-contact associations map to hubspot deal associations, ensuring the deal timeline shows the correct contact history after migration. All association types are preserved during the migration.

The original wired-plus internal record ID is stored on every hubspot record as a custom text field for traceability and to support delta-run de-duplication if a second migration pass is needed. This enables accurate record matching between the two systems.

Wired plus automations are platform-configured and cannot export in a transferable format. They do not migrate. Flitstack exports the workflow logic as a rebuild reference document, and hubspot's workflow tool is used to recreate the logic post-migration. The reference document captures triggers, conditions, and actions for each automation.