Migrate from WORKetc to Salesforce Sales Cloud

WORKetc Contact records map directly to Salesforce Contact. Standard fields (Name, Email, Phone, Address, Title) migrate without transformation. Owner assignment migrates by resolving the WORKetc user email to the Salesforce User email. WORKetc lifecycle fields (status, source, created date) map to Salesforce standard fields or custom fields depending on what the destination org has provisioned.

WORKetc Company records map to Salesforce Account. The Company record is the parent of multiple Contact records, so we create Account first in the migration sequence so that the AccountId lookup is satisfied at Contact insert time. Company-level custom fields map to equivalent Salesforce custom fields, and the Company name becomes the Account Name.

WORKetc Lead records capture early-stage prospects through to conversion. We export the full lead lifecycle including status, source, and converted-flagged records. Converted Leads in WORKetc that were converted to Contact+Company map to Salesforce Lead records with a custom converted_date__c field. Customers who use both Lead and Contact objects in WORKetc should note that Salesforce maintains the same split model.

WORKetc Deals link to Companies and Contacts with stage, amount, and probability fields. We preserve the Deal-to-Company association and map the WORKetc pipeline stage to a Salesforce Opportunity Sales Process or Record Type. Closed-Lost reason and Closed-Won amount migrate to Salesforce standard fields. The WORKetc deal priority flag becomes a custom Opportunity field if the destination org requires it.

Each WORKetc pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process. Stage probability percentages from WORKetc migrate to Salesforce StageProbability values. We configure the destination Sales Process in Sandbox before migration so that stage values are whitelisted per pipeline.

WORKetc Projects use Project Types and Stages for weighted progress tracking, which is non-standard. We export the full project record including stage configuration with custom percentage weights, milestones, and task hierarchies. The stage weight system (e.g., 'Do Work' at 90%, 'Review' at 10%) does not map directly to Salesforce's task-count or duration-based progress, so we convert to a duration-weighted percentage in a custom progress field and document the conversion logic in the migration report. If the destination org does not have the Project Management addon, Projects migrate to a custom Project object with the same fields.

WORKetc Tickets link to Customers, Companies, and Projects with status, priority, and conversation threads. We export ticket records with full conversation history and attachment references. Ticket status maps to Salesforce Case Status, priority maps to Case Priority, and the conversation thread migrates as EmailMessage records linked to the Case.

WORKetc Invoice records include line items, totals, and payment status linked to Customers and Projects. We export invoice headers and line items. Payment history and linked bank transaction records require separate reconciliation because WORKetc's billing module stores these separately from the invoice header. If the destination org requires invoice records, we create a custom Invoice object; otherwise invoice data attaches to the related Opportunity or Project.

WORKetc Custom Field definitions and values are exported, but field types (dropdown, text, date, number) require mapping to equivalent Salesforce field types. We export the custom field schema definition, create equivalent custom fields in the destination Salesforce org (with proper field type mapping), then populate values during the main record migration pass. Picklist values migrate as Active values in the destination picklist field.

WORKetc User records (name, email, role, permission level) map to Salesforce User records by email match. The customer provisions Salesforce Users before migration. Any WORKetc User without a matching Salesforce User goes to a reconciliation queue. Role structures rarely map 1:1 because WORKetc's permission model is flat-rate tier-based and Salesforce uses profile-plus-permission-set assignment.

WORKetc Contractor Portal users are a separate identity class with limited access and may lack standard email addresses or user credentials. They do not map to Salesforce User records because Salesforce does not have a native contractor portal concept. We map Contractor Portal users to Salesforce Contact records with a custom checkbox field is_contractor__c set to true, preserving the contractor's name, company association, and role information.

WORKetc File management stores documents linked to records. We export file metadata (filename, upload date, linked record reference) and URL references. Actual file binary export depends on whether WORKetc exposes the file via its API or UI export. If files are accessible, we upload them to Salesforce as ContentVersion records linked via ContentDocumentLink to the parent record.