Migrate from Workpex to Freshsales

Workpex Leads map directly to Freshsales Leads. If the Workpex account uses a qualification lifecycle (e.g., new leads progress to contacted, qualified, converted), we preserve that status in a custom field on the Freshsales Lead. Freshsales' field-mapping dropdown on the Lead module lets us map lead custom fields to corresponding Contact or Deal fields before conversion; we configure this during the import preparation phase, not after the fact, to prevent silent data loss.

Workpex Contacts map to Freshsales Contacts. Standard fields (name, phone, email, address) map directly. The Contact-to-Lead association from Workpex is preserved by matching on email or external ID during the import so that the relationship context is not lost in Freshsales.

Workpex Companies map to Freshsales Accounts. Company names become Account names, and the Workpex company domain becomes the Website field. If Workpex Companies have a parent-child structure, we map it to Freshsales' Account hierarchy using the parent_account_id lookup.

Workpex Deals map to Freshsales Deals. The dealstage property maps to Freshsales Deal Stage. Pipeline assignments in Workpex map to Freshsales Deal pipelines, which we configure before migration. Any custom pipeline stages defined in Workpex require manual value-mapping in Freshsales' pipeline editor; we flag each one during the pre-migration audit.

Workpex Tasks migrate to Freshsales Tasks with Status (open/closed), Priority, due date, and assignee preserved. Task descriptions migrate as task notes. Assignment is resolved by matching the Workpex user against the Freshsales User record created during the owner migration phase.

Workpex follow-up reminders are tied to Leads and Contacts with a scheduled date and description. Freshsales does not have a native Reminder object. We map reminder dates to a custom date field on the Contact or Lead, and the reminder text as a linked activity note or as a task with the reminder date as the due date. We document this decision during scoping so the customer can choose the representation they prefer.

Workpex call metadata (duration, direction, timestamp, disposition) migrates to Freshsales Task records with TaskSubtype set to Call. Call recordings migrate as file attachments linked to the Task; we flag any recordings in unsupported formats (proprietary binary) for manual upload post-migration.

Each Workpex pipeline stage becomes a Freshsales Deal Stage within the corresponding pipeline. We configure the pipeline structure in Freshsales before import, mapping stage names and ordering 1:1. Custom or deprecated stages are flagged for the customer to review and consolidate before the deal migration runs.

Workpex Users map to Freshsales Users by email match. Any Workpex User without a corresponding Freshsales User is held in a reconciliation queue; the customer's Freshsales admin provisions the missing user before the record import resumes. Owner assignments on Leads, Contacts, Deals, and Tasks are resolved at this stage.

Workpex custom fields on Leads and Contacts are discovered during the scoping audit. We create matching custom fields in Freshsales under the corresponding module (Leads, Contacts, Accounts, Deals) with compatible field types before migration. For any custom field with an incompatible data type (e.g., Workpex stores a multi-select as a pipe-delimited string but Freshsales expects a multi-select picklist), we flag it for transformation and document the transformation logic in the pre-migration report.