Migrate from Trade Service Pro to Salesforce Sales Cloud

Trade Service Pro customer records map directly to Salesforce Account objects. Customer name maps to Account.Name, and the primary phone number maps to Account.Phone. If the customer is a business entity rather than an individual, no further splitting is required.

Trade Service Pro contact records map to Salesforce Contact objects. Each contact requires a parent AccountId — FlitStack AI resolves this by matching the contact's parent customer name to the migrated Account.Name. Unmatched contacts land in a default placeholder account for review.

Trade Service Pro work orders are the core operational record. They map to Salesforce Case records by default. If the organization uses Field Service Lightning, the records are created as ServiceAppointment parent records. Job status (Scheduled, In Progress, Completed, Cancelled) maps to Salesforce Case Status values via value mapping.

Trade Service Pro estimates are pre-job quote documents. They map to Salesforce Opportunity objects with the estimate total as the Opportunity.Amount. Line items from the estimate map to OpportunityLineItems via PriceBookEntry, which requires a Salesforce Product2 record to exist first.

Salesforce has no native invoice object. Trade Service Pro invoice records (including line items, totals, and payment status) migrate to a custom Invoice__c object with an Invoice_Line_Item__c child object. The parent Account lookup resolves via customer name match. During migration, we preserve the original invoice number as a custom field for straightforward cross-referencing and audit trails.

Trade Service Pro timesheet data has no direct Salesforce equivalent. Each time entry migrates as a Time_Entry__c record with a lookup to the parent Job (Case) and to the technician User record. Clock-in and clock-out timestamps preserve as custom datetime fields.

Trade Service Pro staff records map to Salesforce User objects by email match. Technicians who do not have a corresponding Salesforce login are flagged before migration — the team either provisions a Salesforce user or assigns their records to a fallback UserId.

Trade Service Pro file attachments on jobs, invoices, or customers re-upload to Salesforce Files (ContentDocument/ContentVersion model). File size limits apply — Salesforce Files cap at 2GB per file. Inline images in notes are downloaded and rehosted. We also verify file type compatibility and recreate folder structures to maintain organized access in Salesforce.

Trade Service Pro incoming lead or intake records map to Salesforce Lead objects. Lead source, referral information, and ad-source tracking fields map to custom Lead fields. Unqualified leads land as Leads; qualified leads route to the Account–Contact path. We preserve the original lead creation date as a custom datetime field to keep historical timing for reporting.

Trade Service Pro payment records (amount, method, date, gateway status) migrate to a custom Payment__c object with a lookup to the parent Invoice__c record. Payment status (Paid, Pending, Failed) preserves as a custom pick-list field for reconciliation reporting. We also map the gateway transaction ID to a custom text field to support audit and refund workflows.

Any custom properties defined on Trade Service Pro customers, jobs, or invoices migrate as Salesforce custom fields on the corresponding object. The __c suffix is applied per Salesforce convention. Field-level security settings are applied per profile at migration time. We also generate a field mapping worksheet that lists each source field, its destination __c counterpart, and the assigned profile permissions for quick review.