Migrate from WorkBuddy to Salesforce Sales Cloud

WorkBuddy Customer is a combined person-and-organisation record. It splits into Salesforce Account (company name, site address, industry) and Contact (primary contact, phone, email). The customer's primary site address from WorkBuddy becomes the Account billing/shipping address. Additional sites are added as Account Address records.

WorkBuddy Job has no Salesforce standard equivalent. We create a Job__c custom object with fields for job number, site address, job type, status, scheduled start/end, assigned technician, quoted cost, and actual cost. If the job has a revenue value tied to a contract, the financial summary also creates a Salesforce Opportunity for pipeline tracking — linked via a lookup field on Job__c.

WorkBuddy job status values (e.g. Quoted, Scheduled, In Progress, On Hold, Completed, Invoiced, Cancelled) map to a custom pick-list field Job__c.Status__c on the custom object. Where a Job__c has a linked Opportunity, status values map to Salesforce Opportunity StageName per Sales Process — Completed maps to Closed Won, Cancelled to Closed Lost, Invoiced to Closed Won, with intermediate statuses mapping to the corresponding pipeline stage.

The job site address stored on a WorkBuddy Job migrates as the Salesforce Account's ShippingAddress. For multi-site customers, the primary site becomes the Account's primary address; additional sites can be stored as Address records on Account or as a custom Site__c object linked to Account.

WorkBuddy Asset (equipment linked to a customer site) maps to Salesforce Asset. The Asset Name, SerialNumber, install date, and status fields map directly. The WorkBuddy customer link becomes Asset.AccountId via the Account resolved from the customer mapping. Maintenance history stored as WorkBuddy notes migrates as Salesforce Notes attached to the Asset record.

WorkBuddy Quote data (line items, quantities, rates, total) migrates to a Quote__c custom object linked to Job__c. Line items can alternatively map to OpportunityLineItem where the job maps to an Opportunity, preserving product, quantity, and sales price. WorkBuddy quote PDF attachments re-upload as Salesforce Files.

WorkBuddy Subcontractor records (company name, trade, contact, rate) map to a custom Subcontractor__c object. The N:N relationship between WorkBuddy Job and Subcontractor requires a JobSubcontractor__c junction object in Salesforce — fields include assigned trade, hourly rate, and job assignment date. This ensures each subcontractor's role per job is independently tracked.

WorkBuddy Timesheet entries (technician, date, hours worked, job linked) map to Salesforce Tasks (WhoId = Contact, WhatId = Job__c, ActivityDate = date, Description = hours and notes). For billing-rate and cost-tracking data that WorkBuddy timesheets carry, a LabourEntry__c custom object captures billable hours, labour cost, and billable flag per technician per job.

WorkBuddy safety and compliance checklists per job do not have a Salesforce equivalent. We create a Checklist__c custom object as a child of Job__c, with ChecklistItem__c records representing each checklist line (item description, pass/fail flag, notes, completed date). The parent Job__c carries a ComplianceStatus__c pick-list derived from the most recent checklist completion.

WorkBuddy job attachments — photos, signed forms, site sketches, compliance documents — re-upload to Salesforce Files (ContentDocument / ContentVersion model). Files are linked to the corresponding Job__c record via ContentDocumentLink. WorkBuddy PDF report templates have no Salesforce template equivalent — these are preserved as Files and the template rebuild is flagged for your Salesforce admin.

WorkBuddy Users with active assignments resolve to Salesforce Users by email match. A WorkBuddy user who is a field technician and does not have a Salesforce license maps to a Contact record instead — with their Job__c assignments linked via WhatId on Task records. Unmatched technicians are flagged before migration so your team can create Salesforce users or accept the Contact fallback.

WorkBuddy custom fields on any object migrate to Salesforce custom fields (suffix __c) on the corresponding Salesforce object. We create the custom field in Salesforce before the migration batch runs. Data type mapping: WorkBuddy text → Salesforce Text(255) or Long Text Area; number → Number; date → Date; pick-list → Pick-list; checkbox → Checkbox. Validation rules on Salesforce custom fields are noted for post-migration review.