Migrate from JobTread to Microsoft Dynamics 365 Sales

JobTread customers (organizations) map directly to Dynamics 365 Sales Account records. The Account.Name, Website, and address fields transfer as-is without transformation. Customer contacts migrate separately as Contact records and attach to the Account via the parent customer link field. Any custom properties defined on the JobTread customer record migrate as custom fields on the Account object in Dynamics 365 Sales.

Named contacts on JobTread customers map to Dynamics 365 Sales Contact records. Each contact links to its parent Account via the AccountId lookup field. Email addresses, phone numbers, and job titles transfer directly using standard field mappings. Any custom contact properties defined in JobTread migrate as custom fields on the Contact record, preserving all extended data captured during the customer relationship.

JobTread vendors are organizations tracked for purchasing and subcontractor management. They migrate as Dynamics 365 Sales Account records with a Vendor_Type__c custom pick-list field set to 'Subcontractor' or 'Supplier' to distinguish them from customer accounts. This vendor type marker prevents sales reps from accidentally opening vendor records when expecting pipeline data, maintaining clean segmentation between your supply chain contacts and prospective clients.

Vendor contacts migrate as Dynamics 365 Sales Contact records attached to the vendor Account. The same field-mapping rules apply as for customer contacts — email, phone, and title transfer directly. Vendor contacts use the same AccountId lookup mechanism to associate with their parent vendor organization, ensuring your subcontractor and supplier contact lists remain properly organized in the CRM.

JobTread Jobs map to Dynamics 365 Sales Opportunity records. The job name becomes Opportunity.Name, and job status maps to Opportunity Stage (Proposal, Won, Lost, etc.). Original create date and owner are preserved through custom fields since Dynamics 365 Sales sets CreatedOn at migration time. All construction metadata — job type, address, specifications, and custom properties — migrates as custom fields on the Opportunity record.

JobTread Estimates map to Dynamics 365 Sales Quote records linked to the corresponding Opportunity. Line items from the estimate transfer as Quote Details (product lines) referencing the migrated Product records. Total estimate value maps to Quote Amount. Estimate status (Draft, Sent, Accepted, Revised) maps to the Quote status field, preserving the complete lifecycle of each estimate through the sales process.

JobTread Cost Items in the catalog migrate as Dynamics 365 Sales Product records. Unit cost from JobTread maps to Product's StandardCost field for margin calculations; sales price maps to List Price. Cost Group names migrate as a custom CostGroup__c text field on the Product record, preserving your catalog organization structure for estimating and purchasing workflows.

JobTread specifications are structured data attached to jobs describing materials, methods, or requirements. Dynamics 365 Sales has no native specification object equivalent. We create a custom table (Job_Specification__c) on Dataverse with fields for Specification_Type__c, Description__c, and a lookup field pointing to the parent Opportunity record, enabling full specification traceability within the CRM.

JobTread tasks attached to jobs or customers migrate as Dynamics 365 Sales Task records. The Subject, due date, priority, and status fields transfer directly using identical field names. The Regarding (parent record) field links to the corresponding Opportunity or Account based on the task's context in JobTread, maintaining the relationship hierarchy across both systems.

JobTread notes migrate as Dynamics 365 Sales Note (Annotation) records. The subject line and body text transfer completely, preserving all historical commentary. Notes attach to the parent Account, Contact, or Opportunity based on the note's context in JobTread, ensuring conversations and context follow the relevant record through the migration.

JobTread workflows do not migrate automatically — there is no equivalent automation framework between the platforms. We export workflow definitions (triggers, conditions, actions) as JSON documentation for your Dynamics 365 admin to rebuild in Power Automate. The exported file includes every active workflow's complete logic, including field references that must be updated to point to your new Dynamics 365 custom field names.

JobTread custom fields defined on Jobs migrate as custom fields on the Dynamics 365 Sales Opportunity object. Field type mapping follows standard conventions: text fields map to Single Line of Text, numbers map to Whole Number or Decimal depending on precision requirements, and picklist values map to Choice fields in Dataverse, maintaining data integrity throughout the migration.

JobTread Selections are structured options offered to clients during the estimate phase, such as flooring upgrades, fixture choices, or material substitutions. Dynamics 365 Sales has no native equivalent for selection management. We create a Selection__c custom table linked to the Opportunity with fields for Selection_Group__c, Option_Name__c, and Price_Adjustment__c, preserving your selection workflow within the CRM.