Migrate from Trade Service Pro to Freshsales

TSP customer records map directly to Freshsales Contacts. The TSP contact's name, email, phone, and address fields map to Freshsales Contact fields. TSP allows multiple contact roles per customer — the primary contact role becomes the Freshsales Contact record; additional roles are captured in Freshsales Contact Relationship entries.

TSP company-level records map to Freshsales Accounts. Business name, domain/website, industry classification, employee count, and address fields map directly. TSP's parent-company hierarchy (if used) maps to Freshsales Account hierarchy via the Parent Account lookup field. When TSP includes multi-location branch offices under a parent company, these translate to child Account records linked through the parent Account relationship, preserving the organizational structure in Freshsales.

TSP jobs and work orders are the primary translation unit. Active jobs map to Freshsales Deals in the appropriate pipeline stage based on TSP job status: 'Scheduled' or 'In Progress' maps to Freshsales 'In Progress' or 'Qualified' stages; 'Completed' maps to 'Proposal Sent' or 'Negotiation'; 'Invoiced' maps to 'Closed Won'. Job type (trade category — electrical, plumbing, HVAC) is preserved as a custom Deal field.

TSP estimates and their line items merge into a Freshsales Deal with product entries. The estimate total maps to Deal Amount; individual line items (labor rate, parts, permits) map to Deal Product entries under the Freshsales Product Catalog. If TSP estimate line items use custom pricing that does not exist in Freshsales, those products are created during migration.

Freshsales has no native invoicing object. TSP invoice records (total amount, payment status, payment method, balance due) are preserved as custom fields on the corresponding Deal record, and the invoice PDF is stored as a Freshsales File attachment. For teams requiring full invoice history, Freshsales CPQ add-on or an external accounting integration (QuickBooks, Xero) must be set up post-migration.

TSP custom forms capture industry-specific data — license numbers, trade certifications, service-area codes, property access notes. These translate to Freshsales custom fields on the appropriate object (Contact for customer attributes, Account for property/business attributes, Deal for job-specific fields). Each TSP custom form template generates a group of custom fields in Freshsales. Field type is mapped: text to text, numeric to number, date to date, pick-list to pick-list.

TSP user records are resolved to Freshsales users by email match. TSP owner assignments on jobs, estimates, and customers map to Freshsales Deal Owner, Contact Owner, and Account Owner fields. TSP staff without an email match are flagged during pre-flight validation; their records are assigned to a designated fallback Freshsales user until your team invites the correct user.

TSP file attachments — job photos, signed estimates, inspection forms — are downloaded and re-uploaded to Freshsales Files, linked to the corresponding Contact, Account, or Deal record. Freshsales file storage limits vary by plan: Growth includes 2GB/user; Pro includes 5GB/user; Enterprise includes 100GB/user. Large file sets may require plan upgrade or selective attachment migration.

TSP scheduling and dispatch data (technician assignments, route order, GPS coordinates) has no Freshsales equivalent. We preserve the technician name and scheduled date as a custom field on the Deal record for reference, but the scheduling model cannot be reproduced in Freshsales without a dedicated field-service add-on (such as Freshservice FSM or a third-party integration).

TSP timesheet records — clock-in times, break durations, job timers — cannot map to Freshsales standard objects. Labor hours associated with a job are preserved as custom numeric fields on the corresponding Deal record for historical reference. Payroll-grade timesheet data should be exported from TSP as a CSV report and managed in a separate time-tracking system post-migration.