Migrate from Workpex to HubSpot

Workpex leads carry contact details and a status field. FlitStack maps the contact properties to HubSpot Contact fields and sets lifecycle_stage based on Workpex status: 'Qualified' and 'Customer' route to 'customer', 'New' and 'Contacted' map to 'lead'. Unmatched statuses land as 'subscriber' by default for manual review.

Workpex contacts without a status qualifier migrate directly to HubSpot Contacts preserving first name, last name, email, phone, job title, and address fields. Owner resolution happens by email match against HubSpot user list before the contact lands. All associated activity history moves with the contact record.

Workpex company records map 1:1 to HubSpot Companies. Company name, domain, industry, employee count, and annual revenue translate to HubSpot's matching properties. Parent-child company hierarchies in Workpex map to HubSpot's associated companies model. This preserves organizational context for downstream reporting.

Workpex deals with deal name, amount, stage, and close date map to HubSpot Deals. Pipeline and stage are resolved by matching Workpex stage names to HubSpot pipeline stage values; multiple Workpex pipelines each get their own HubSpot pipeline with stage probability applied per destination stage.

Workpex follow-up reminders with due dates and descriptions become HubSpot Tasks with subject, body, and due date. The original reminder timestamp is preserved as a custom datetime property since HubSpot tasks do not retain their own create-date for scheduling independently of the record.

Workpex call logs with duration, direction (inbound/outbound), and outcome map to HubSpot call engagements and a linked Task. HubSpot's call recording attachment migrates as a file re-uploaded to the contact or deal record's file attachment section with original call metadata preserved in task notes.

Workpex custom fields on leads, contacts, and deals create HubSpot custom properties in the destination portal before migration. Text, number, date, and pick-list types map directly; Workpex pick-list values require HubSpot enumeration options to be pre-created with matching labels so the migration can apply value-mapping at import time.

Workpex user IDs are resolved by matching owner email to HubSpot user email addresses. Users in Workpex who have no HubSpot account are flagged pre-migration so the team can either invite them to HubSpot or assign their records to a fallback owner before the migration runs.

Workpex notes with body text and timestamps map to HubSpot notes attached to the relevant contact, company, or deal record. HubSpot note associations are created during migration to maintain the original note-to-record relationship from Workpex. This ensures context is preserved across all linked entities.

Workpex file attachments on leads, contacts, and deals are downloaded and re-uploaded to the corresponding HubSpot records as Files. HubSpot's 115 MB file size limit applies; files exceeding this are flagged for compression or manual handling before the migration batch runs.

Workpex workflow rules, automated sequences, and reminder logic are platform-specific automation that does not exist in the data layer. These must be rebuilt in HubSpot's workflow builder post-migration. FlitStack exports Workpex workflow definitions as a structured reference document for the HubSpot admin to use during rebuild.

Workpex tracks lead status transitions with timestamps. Since HubSpot's lifecycle_stage property records only the current value, FlitStack preserves the status-change history as a custom multi-line text property (Lifecycle_History__c) containing timestamped status entries from Workpex for audit continuity. This maintains full visibility into the lead progression timeline.