Migrate from JobTread to Salesforce Sales Cloud

JobTread customers map directly to Salesforce Accounts. We preserve the original create date as Original_Create_Date__c because Salesforce's CreatedDate reflects migration time rather than the original record creation. Company-level custom fields migrate as Account __c fields on the mapped Account record. All customer attributes including billing address, phone, and email transfer to the corresponding Salesforce Account fields.

JobTread customer contacts map to Salesforce Contacts linked via AccountId to their parent Account. Primary contact role (primary, billing, site contact) maps to Salesforce Contact Roles on the Account object. Contact-level custom fields become Contact __c fields, preserving all custom data associated with each individual contact record in JobTread.

JobTread Jobs map to Salesforce Opportunities. The job name becomes Opportunity Name, the budget amount maps to Amount, and close date becomes CloseDate. JobTread's job status (Active, Completed, On Hold) maps to a custom pick-list Job_Status__c on Opportunity, not to standard StageName — since Salesforce stages represent sales pipeline, not construction lifecycle.

JobTread cost items (materials, labor, equipment) link to a Job. We map them as Salesforce Opportunity Line Items with a custom JobTread_Cost_Category__c field storing the original category name, and JobTread_Cost_Item_ID__c storing the source reference for traceability and de-duplication during future delta syncs. Each line item preserves quantity and unit cost data.

JobTread vendors map to Salesforce Accounts tagged with a Vendor Record Type to distinguish them from customer Accounts. Vendor-level custom fields migrate as Account __c fields. Vendor contacts map to Salesforce Contacts under the vendor Account. The Vendor Record Type enables separate page layouts and reporting tracks for vendor relationships versus customer accounts.

Vendor contacts map to Salesforce Contacts under the vendor Account. Role and contact-specific custom fields become Contact __c fields. We link them to the vendor AccountId, not the customer Account, ensuring vendor contacts appear under the correct vendor Account hierarchy in Salesforce. Contact roles on the vendor Account can further classify their function.

JobTread documents and attachments linked to Jobs, Customers, or Vendors re-upload to Salesforce Files. They are associated to the corresponding Account or Opportunity record. File size limits (25MB per file in Salesforce) apply — large files flagged before migration for manual handling or alternative transfer methods.

JobTread's custom fields apply to Customers, Customer Contacts, Jobs, Vendors, Vendor Contacts, and Cost Items. Each custom field needs a Salesforce __c equivalent pre-created in Setup before the migration run. FlitStack delivers a field creation manifest listing every custom field, its type, and target object.

JobTread workflows (triggers, filters, actions) have no Salesforce equivalent. We export workflow definitions as a structured JSON reference document and provide a comprehensive Flow-rebuild guide so your Salesforce admin can recreate each automation step by step with clear mapping from the original JobTread workflow logic to Salesforce Flow components.