Migrate from Workpex to Microsoft Dynamics 365 Sales

Workpex Leads map directly to Microsoft Dynamics 365 Lead records. The primary key is the Lead's email address or an assigned Workpex ID used as an external identifier. Lead Status from Workpex (for example, New, Contacted, Qualified, Converted) maps to the Dynamics 365 Lead Status picklist, which must be reviewed against the destination's active Sales Process configuration. Any Workpex custom fields on Lead (for example, lead source details or segmentation flags) are discovered during the pre-migration audit and created as custom fields on the Dynamics 365 Lead entity before import.

Workpex Contacts map to Dynamics 365 Contact records. Contact-to-Lead associations are preserved by matching on email address and cross-referencing the Workpex relationship table during import. The Dynamics 365 Contact entity receives the mapped fields (name, phone, email, address) and any Workpex custom fields that apply to Contact rather than Lead. Parent Account resolution happens in a separate import phase before Contact insert to satisfy the AccountId lookup.

Workpex Companies map to Dynamics 365 Account records. The Workpex Company name becomes the Account Name, domain data becomes the Website field, and the address fields map to the standard Dynamics 365 address composite. Any custom fields on the Workpex Company object (for example, industry classification or segment flags) are created as custom fields on the Dynamics 365 Account entity. Workpex Companies with a flat structure map to a single Account; if Workpex exposes a parent-company hierarchy, we map it to the Account Hierarchies feature in Dynamics 365.

Workpex Deals map to Dynamics 365 Opportunity records. The Workpex deal amount, close date, and pipeline stage migrate as EstimatedValue, EstimatedCloseDate, and StageName respectively. The pipeline stage name from Workpex must be mapped to a valid Microsoft Dynamics 365 Sales Process stage value, which requires pre-migration configuration of the Sales Process and Record Type in the destination org. Any custom deal fields (for example, win probability, competitor flags, or product interest) are created as custom Opportunity fields before import.

Workpex pipeline stages define the deal lifecycle and map to Dynamics 365 Record Types (one per Workpex pipeline) and Sales Process stage values. We create the Record Type in Dynamics 365 before migration, assign it to the Opportunity import batch, and configure the Sales Process so that each stage name from Workpex appears as a valid StageName value in the destination. Probability percentages from Workpex migrate to the StageProbability field on each stage step. Deprecated or inactive Workpex stages are archived rather than mapped.

Workpex Tasks migrate to Dynamics 365 Task records. The task subject, description, due date, priority, and status (open or completed) transfer directly. Task assignees are resolved by matching the Workpex owner email against the Dynamics 365 User table during import. Any open Task records in Workpex at migration cutover are flagged for re-assignment to the appropriate Dynamics 365 User after cutover.

Workpex Follow-up Reminders are tied to Leads and Contacts and contain a date and a description. Dynamics 365 does not have a native Reminder object, so we map Reminder dates to a custom date field (for example, nextfollowupdate_custom__c) on the Contact or Lead record, and the Reminder description is stored as a Note attached to the same record. During scoping, the customer chooses whether to create a dedicated custom field or use Notes as the primary carrier for reminder data.

Workpex Call Records migrate to Dynamics 365 Task records with TaskSubtype set to Call. Call metadata (duration, direction, timestamp, disposition) transfers to custom fields on the Task record. Call recording files exported from Workpex are attached to the corresponding Task record via ContentDocumentLink or stored in a SharePoint folder linked to the Contact or Account. Recording format compatibility (for example, MP3 versus WAV) is verified during the pre-migration audit; incompatible formats are flagged for manual download and re-upload.

Workpex Users and Owners referenced on Leads, Deals, Tasks, and Call Records are mapped to Dynamics 365 Users by email address match. Any Workpex Owner without a corresponding Dynamics 365 User is held in a reconciliation queue for the customer's admin to provision before record import resumes. User active or inactive status from Workpex maps to the corresponding IsActive flag in Dynamics 365.