Migrate from Workpex to Salesforce Sales Cloud

Workpex Leads map directly to Salesforce Lead. The Workpex Lead status, source tracking, and user assignment fields migrate to Salesforce Lead Status, LeadSource, and OwnerId respectively. We resolve OwnerId by email match against the Salesforce User table and hold unresolved owners in a reconciliation queue for admin provisioning. Any Workpex custom fields on Lead are discovered during the pre-migration audit and mapped to Salesforce custom fields of matching type before import.

Workpex Contacts map to Salesforce Contact with the standard name, phone, email, and address fields migrated directly. Contact-to-Lead associations from Workpex are preserved by mapping the Workpex contact_id to a custom external ID field on Contact, allowing cross-referencing after migration. Contacts are imported after Accounts so that the AccountId lookup is satisfied at insert time.

Workpex Company records map to Salesforce Account. The Workpex company domain or website field becomes the Account Website field and is used as the dedupe key during import to prevent duplicate Accounts. If Workpex Companies have a nested or hierarchical structure, we map the parent-company relationship to the Salesforce Parent Account lookup.

Workpex Deals map to Salesforce Opportunity. The Workpex dealstage property maps to Salesforce StageName, and the associated pipeline assignment maps to a Salesforce Record Type and Sales Process that we configure before migration. Closed-Won and Closed-Lost values from Workpex become Salesforce Probability and Amount fields. Deal owner assignment migrates via the Owner email lookup established in the User mapping phase.

Each Workpex pipeline stage value maps to a Salesforce StageName entry within the target Sales Process. Stage probability percentages migrate from Workpex to Salesforce StageProbability. Any deprecated or custom-only stages in Workpex are flagged for value-mapping review before import so that the Sales Process whitelist matches what the team actually uses.

Workpex Tasks migrate to Salesforce Task with Status, Priority, ActivityDate, and Subject preserved. Task assignment migrates by resolving Workpex owner references to Salesforce OwnerId via the User mapping. Overdue and stagnant task flags from Workpex are stored in custom Task fields if the destination Salesforce org has active alerts enabled.

Workpex Follow-up Reminders are tied to Leads and Contacts. Reminders with a future date migrate to Salesforce Task records with the original timestamp preserved as ActivityDate. Reminders without a date migrate as Tasks with a custom Reminder_Type__c field set to Follow-up to distinguish them from standard to-dos. Reminder descriptions migrate as Task Description.

Workpex call metadata (duration, direction, timestamp, disposition) migrates to Salesforce Task with TaskSubtype = Call. Call duration in seconds migrates to CallDurationInSeconds, and disposition notes migrate to a custom Call_Disposition__c field. Call recordings are flagged for separate file transfer as ContentDocument records linked via ContentDocumentLink; playback format compatibility is validated before upload.

WhatsApp message logs and marketing records from Workpex migrate as Salesforce Task records with a custom WhatsApp_Source__c field set to Workpex. Message body content migrates as Task Description, and any media attachments are stored separately and linked via ContentDocumentLink. Because WhatsApp message threading does not map to a native Salesforce object, we store the conversation as a flat activity record. Teams requiring native WhatsApp integration in Salesforce should evaluate Salesforce's own WhatsApp Business integration post-migration.

Facebook Ad management data stored in Workpex migrates to Salesforce Campaign records. Campaign Name carries the Workpex ad or campaign identifier, and source attribution (UTM parameters, referrer, ad ID) is stored in custom Campaign fields. Campaign members are created by linking the relevant Contacts and Leads to the Campaign, and lead-source mappings from Workpex are preserved in a custom field for attribution reporting.

Workpex Users and Owners are mapped to Salesforce User records by email address. We extract every distinct owner referenced on Leads, Contacts, Deals, Tasks, and Call Records and match against the Salesforce User table. Users without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import begins. OwnerId references on all standard objects are populated after this step is validated.

Workpex custom fields on Leads and Contacts are discovered during the pre-migration audit by enumerating every account configuration. Each Workpex custom field maps to a Salesforce custom field of equivalent data type (text, number, date, picklist, checkbox). The Workpex field label becomes the Salesforce field label, and the API name is derived from the Workpex field name with a custom field prefix. Any fields with incompatible data types are flagged for manual mapping.

File attachments associated with Leads, Deals, or Tasks in Workpex export as binary files or links. We migrate them as Salesforce ContentVersion records, creating ContentDocument records linked via ContentDocumentLink to the parent Lead, Contact, Account, or Opportunity. Files exceeding Salesforce's 25 MB per ContentVersion limit or in unsupported binary formats are flagged for manual upload after go-live.

Workpex GPS tracking data has no documented schema, so we discover the data structure during the scoping phase by analyzing sample exports or database records. Latitude and longitude values migrate to Salesforce custom number fields on the relevant object, or are stored as a custom location composite field. If the GPS data is in a proprietary binary format, we flag it for manual review and export and document the format in the pre-migration audit report.

Workpex Links between Leads and Contacts are preserved in Salesforce via a custom external ID field workpex_lead_id__c on Contact that references the original Workpex lead ID. This allows cross-object reporting and relationship queries after migration without requiring a custom junction object.

The consolidated activity timeline in Workpex (calls, follow-up tasks, reminders, WhatsApp logs) migrates as Salesforce Tasks and Events in chronological order. The original Workpex timestamp becomes the ActivityDate on each migrated record, preserving the timeline order that sales reps rely on for deal history review. We migrate as many activity record types as the Workpex export can produce; any engagement records missing from the export are flagged in the audit report.