Migrate from Jobsite Mobile to Salesforce Sales Cloud

Jobsite Mobile worker records map directly to Salesforce Contact. Active workers land as Contacts with an IsActive__c custom flag; inactive workers may be mapped to Lead based on your specified rule. Salesforce requires AccountId for most Contact queries — workers without a primary company get assigned to a default 'Unassigned' Account record.

Only Jobsite Mobile workers with an active Salesforce User license and profile get mapped to User records. Owner resolution happens by email match. Workers without a matching Salesforce user are flagged pre-migration — your team invites them to Salesforce or assigns them to a fallback User as OwnerId.

Jobsite Mobile company records map to Salesforce Account. Parent-company hierarchies in Jobsite Mobile migrate to Salesforce ParentId on Account. Multi-location companies get one Account with multiple Address records (via the Salesforce Address object) or custom address fields per location. We also map the primary billing and shipping addresses to standard Account fields, and any additional custom address properties are added as custom fields on Account for complete coverage.

Jobsite Mobile job records require a custom Work_Order__c object in Salesforce since Salesforce Sales Cloud has no native work-order object. Your admin creates Work_Order__c with RecordTypeId per job type before migration. Job status maps to a custom Status__c pick-list field; stage/probability are not applicable to work-order records unless you are mapping Jobs to Opportunities.

Jobsite Mobile job status values (Open, In Progress, Completed, Cancelled, On Hold) map to custom pick-list values on Work_Order__c.Status__c. Each value requires a corresponding pick-list entry in Salesforce — we generate the value map during the discovery phase. During the mapping, we also verify that each status maps to the appropriate RecordTypeId, ensuring that status visibility aligns with job type in Salesforce.

Jobsite Mobile worker-to-job assignments require a custom junction object (Assignment__c) with lookup fields to Contact (Worker) and Work_Order__c (Job). This preserves the many-to-many relationship that Jobsite Mobile natively supports. Assignment records carry Scheduled_Start__c and Scheduled_End__c datetime fields migrated from Jobsite Mobile's scheduling slots.

Alternatively, FlitStack can map Jobsite Mobile assignments to Salesforce Task records linked to the Work_Order__c. This uses Salesforce's built-in TaskWhatId and TaskWhoId fields, simplifying reporting but losing some custom assignment metadata. Your team chooses the model during scoping. If you select the Task model, any custom fields on the Assignment__c object that are not native to Task will be omitted, so we recommend documenting those fields early in scoping.

Files attached to Jobsite Mobile job records (photos, signed forms, inspection reports) re-upload to Salesforce Files linked to the Work_Order__c record. Salesforce Files respect the 25MB per-file limit. Inline images in notes are extracted and rehosted as Salesforce Files with ContentDocument links.

Jobsite Mobile job notes migrate to Salesforce Notes (legacy Note object) or ContentNote (Lightning-ready rich-text notes). Original timestamps and author references are preserved in Salesforce's CreatedDate and CreatedById fields, with the original note text stored in Body or Content fields respectively.

Jobsite Mobile custom properties on Worker records (certification type, employment status, skills list) migrate as custom fields on Salesforce Contact with __c suffix. Multi-select pick-list values in Jobsite Mobile map to Salesforce multi-select pick-list fields. Your admin pre-creates these fields before the migration loads records.

Jobsite Mobile custom properties on Job records (job type, trade category, billing code, estimated duration) migrate to custom fields on Work_Order__c. Pick-list value sets need to be created in Salesforce first — FlitStack generates the pick-list value map during the field-mapping phase and your admin creates the values in Setup.

Jobsite Mobile workflow rules, triggers, and scheduling automations do not migrate to Salesforce. Salesforce Flow must be built separately to replicate the logic. FlitStack exports Jobsite Mobile workflow definitions as a structured document your Salesforce admin or FlitStack's automation team can use as a rebuild reference.