Migrate from Service Toolz to Salesforce Sales Cloud

Service Toolz Customers map directly to Salesforce Accounts. Service Toolz stores company name, address, phone, and industry as top-level customer properties — all map to standard Account fields including Name, BillingStreet, BillingCity, BillingState, BillingPostalCode, Phone, and Industry. Parent-child customer hierarchies in Service Toolz map to Account.ParentId in Salesforce to preserve organizational structure across both platforms.

Service Toolz Contacts map 1:1 to Salesforce Contacts. Each Contact requires an AccountId lookup — Service Toolz contacts without a primary customer get attached to a default 'Unassigned Account' record. Original create dates are preserved in a custom datetime field since Salesforce CreatedDate reflects migration time rather than the original record creation date.

Salesforce has no native work-order object in Sales Cloud. We create a Work_Order__c custom object with fields for job description, status, priority, scheduled date, and technician assignment. The custom object is linked to Account and Contact via lookup fields. Job-status history from Service Toolz is preserved as a custom text area field for audit purposes.

Service Toolz technicians are not a native CRM object. We create a Technician__c custom object for historical records and resolve active technicians to Salesforce User accounts by email match. Unmatched technicians are flagged for your admin to either create Salesforce users or assign to a fallback owner before migration.

Service Toolz products map to Salesforce Product2 records with name, product code, and description. Inventory levels from Service Toolz are stored in a custom field on Product2 (Inventory_Qty__c). Each product also gets a standard PricebookEntry linked to your Salesforce pricebook.

Service Toolz quotes map to a custom Service_Quote__c object linked to Account when Salesforce CPQ is not in use. When Salesforce CPQ is present, quotes map to the standard Salesforce Quote object tied to Opportunities — this requires your admin to configure the CPQ pricebook and quote templates before migration data lands.

Each Service Toolz work-order line item (covering labor hours, parts used, and travel charges) becomes a Work_Order_Line__c record linked to the parent Work_Order__c via a lookup relationship. Line-item type classification such as labor versus parts versus travel is stored as a pick-list field on the child record for filtering and reporting. Products referenced on lines are resolved to Salesforce Product2 records during the mapping phase.

Service Toolz invoices map to a custom Service_Invoice__c object holding invoice number, amount, status, and issue date. If Salesforce CPQ and Contracts are in use, accepted quotes and invoice data can be linked to Opportunities and Contracts — your Salesforce admin configures this schema before migration.

Service Toolz activity logs including job completion notes, dispatch updates, and internal communications map to Salesforce Task records. Site visits with start and end timestamps map to Salesforce Event records representing scheduled appointments. All original timestamps and technician-owner IDs are preserved in custom fields. Activity type is stored in the Task.Type pick-list field for categorization and reporting purposes.

Service Toolz custom fields on any object become Salesforce custom fields on the target object. Text fields become Text(255), pick-lists become pick-lists, numeric fields become Number. We create custom fields via the Salesforce Metadata API before inserting records. Field-level security and page layout assignments are surfaced in the migration plan for your admin.