Migrate from Workpex to Pipedrive

Workpex Leads map directly to Pipedrive People. Standard fields including name, phone, email, address, and lead status transfer 1:1. We preserve the lead source and assignment to Workpex user as custom fields and Owner assignment respectively. Any Workpex lead with a null email address is flagged during the export audit because Pipedrive requires an email for People created via API unless the account has email-optional settings configured.

Workpex Contacts map to Pipedrive People with the Contact-to-Lead association preserved. We create a Person record once per unique email address and deduplicate on email during the import phase. Workpex Contact records without an associated email are flagged for manual review because they may represent duplicate accounts with incomplete data.

Workpex Company records map to Pipedrive Organizations. The Company name becomes the Organization name, and Workpex contact details map to Organization address and phone fields. If Workpex stores a flat hierarchy of parent-child companies, we map them as separate Organizations and note any hierarchical relationship for manual re-creation in Pipedrive's Organization hierarchy view.

Workpex Deals map to Pipedrive Deals with pipeline stage values transformed to match the destination pipeline configuration we build before migration. The Deal value, expected close date, and owner assignment transfer directly. Any deprecated or custom stage names in Workpex are flagged for explicit value mapping during the pre-migration scope review. Closed-Lost and Closed-Won statuses map to Pipedrive's StageWon and StageLost values.

Workpex Tasks migrate to Pipedrive Activities. Status (open/closed), priority, due date, and assignee assignment transfer directly. Task description maps to the Activity subject or note body. Completed tasks preserve their completion timestamp as the ActivityDate for timeline ordering. We resolve Hubspot Owner assignments by email against Pipedrive Users before inserting Activity records.

Workpex Follow-up Reminders attached to Leads and Contacts merge into Pipedrive Activity records linked to the corresponding Person. Reminder dates and descriptions become Activity due dates and subject lines respectively. Overdue alert flags are stored as custom fields on the Activity or the Person record. Because Pipedrive does not have a native Reminder object, all reminder data is modeled as time-bound Activities with type set to Follow-up.

Workpex call records migrate as Pipedrive Activities with type Call. Call duration, direction (inbound/outbound), timestamp, and disposition map to custom Activity fields. Call recording files are flagged for separate handling: we export them as file attachments and link them to the corresponding Activity record, noting that the customer should verify playback format compatibility post-migration.

Each Workpex pipeline stage name and order transfers to a Pipedrive Deal stage within the configured pipeline. We create the pipeline and stages in Pipedrive before Deal migration begins. Stage probability percentages are assigned per Pipedrive's defaults or as specified by the customer's admin during scoping. Custom stage labels are preserved as stage names; any deprecated stages used in historical Deals are retained as inactive stage values.

Workpex Users and Owners map to Pipedrive Users by email address. Active Workpex users become active Pipedrive users. Any Workpex Owner records without a matching Pipedrive User are held in a reconciliation queue for the customer to provision matching Users before record migration resumes. Inactive Workpex users can be mapped as inactive Pipedrive users to preserve historical assignment on Deals and Tasks.

Workpex custom fields on Leads and Contacts are discovered during the pre-migration audit. We create corresponding custom fields in Pipedrive with type-mapped field types (text, number, date, dropdown) and then populate them during the People import. Any custom field with an incompatible data type (for example, Workpex storing structured JSON in a text field) is flagged for transformation logic before import.