Migrate your Trade Service Pro data

Customers are the core CRM object in Trade Service Pro, storing contact details, address, and job history. We migrate these as standard contact records and preserve associated proposals, invoices, and jobs via foreign key mapping during export.

Proposals are tied to Customers and include line items, pricing, and eSign status. We map proposal fields to destination equivalents but flag eSign completion status as it may not carry over to systems without eSign integration.

Invoices contain line items, payment status, and customer references. We map invoice totals and line items cleanly; payment status (paid/unpaid) must be validated post-migration since TSP payment state may not export completely.

Jobs are the primary work-order entity in TSP. They include scheduling, assigned users, and customer references. We map job status, dates, and assignments; custom job fields require field-level mapping against the destination schema.

Intake tracks incoming leads and ad sources before they become jobs. We map lead source, contact info, and status. Lead-to-job conversion history is preserved where TSP exports it, otherwise we flag incomplete conversions.

Timesheet records include clock in/out times, job timers, and break timers tied to users and jobs. We map employee, date, hours, and job association. Timer state (active/paused) does not carry over in CSV exports.

User roles and permissions are system-level settings that do not have a migration path. We export user accounts and map them to roles in the destination platform, but permission sets must be rebuilt manually.

Payment records are tied to invoices and include transaction IDs and amounts. We map payment history to the destination accounting or billing module. TSP's integrated payment processor does not export transaction tokens for reactivation elsewhere.

Attachments on jobs, proposals, and invoices are exported as file references or downloaded blobs where TSP allows bulk downloads. We preserve file names and associate them with their parent records. Large attachment volumes may require chunking.

Schedule entries are tied to Jobs and include date, time, assigned technician, and status. We map these to destination calendar or dispatch objects. Recurring schedule patterns may not export and must be reconstructed.