Migrate from Trade Service Pro to Zoho CRM

Trade Service Pro stores customer name, company name, email, phone, and service address in a single flat record. Migration splits this into a Zoho Account (company name, service address, industry) and a Zoho Contact (customer name, email, phone, job title, Title). The Account-Contact relationship is established via the Account Name lookup on the Contact record. When TSP records have no separate company name, the Contact name is duplicated into the Account Name field to ensure the Contact has a valid AccountId.

TSP proposals map to Zoho Deals. The Deal Name carries the TSP proposal title, Amount maps from the total proposal value, and Stage maps from TSP proposal status using a value-mapping table (Draft → Qualification, Sent → Proposal/Price Quote, Accepted → Closed Won, Declined → Closed Lost). TSP proposal line items migrate as Zoho Products linked to the Deal via Deal-Product junction records. Custom fields capture TSP-specific properties like Proposal_Status__c, Accepted_Date__c, and Expiration_Date__c.

TSP invoices carry invoice number, amount, balance due, status, and dates. If your TSP setup uses invoices primarily as billing records, they migrate to Zoho Deals with Invoice_Number__c, Balance_Due__c, and Invoice_Date__c as custom fields, and Stage set to reflect the invoice payment status (Sent → Open, Paid → Closed Won, Overdue → Negotiation). For high invoice volumes, a separate Zoho custom Invoice module is recommended; this requires custom module creation during schema setup.

TSP payment records (amount paid, payment date, payment method, card type, transaction ID) have no native Zoho equivalent. Low-volume setups map these as custom fields on the parent Deal: Payment_Amount__c, Payment_Date__c, Payment_Method__c, Transaction_ID__c. For businesses with recurring payment history, a custom Payment module is created in Zoho with a lookup to the parent Deal, preserving the one-to-many relationship from a single Deal to multiple Payment records.

TSP user records — including name, email, role, and phone — are resolved by email match against Zoho CRM users. If a TSP user email matches an existing Zoho user, their User ID becomes the OwnerId on all records they own. If no match is found, records are assigned to a designated fallback Zoho user and Source_Owner_Email__c is preserved as a custom field for post-migration manual reassignment. TSP role names are stored in a Role_Mapping__c custom field for your Zoho admin to map to Zoho Profiles and Roles.

TSP notes migrate to Zoho Notes attached to the parent Account or Contact record. The Note Title carries the TSP note subject; the Note Body carries the full note content. Created timestamps and note owners are preserved. Note that TSP notes with rich-text formatting are stripped to plain text on import, as Zoho Notes does not natively render HTML-formatted content.

TSP file attachments linked to customers, proposals, or invoices migrate as Zoho Attachments with the parent record ID preserved. Files are re-uploaded to Zoho's storage under the corresponding Account, Contact, or Deal. Each attachment retains its original filename and, where available, the Created Date from TSP. Large files that exceed Zoho's 25 MB per-attachment limit are flagged before migration so your team can decide whether to host externally and link by URL.

TSP intake records capturing how a customer first reached the business (referral source, ad campaign, walk-in) have no direct Zoho equivalent. These migrate as a Lead_Source_Detail__c custom pick-list field on the Contact record, with TSP's intake values preserved as pick-list options. If your TSP setup captures intake as a separate module rather than a property, a custom Intake custom module is created in Zoho with a lookup to the parent Contact.

TSP job records with scheduled date, assigned technician, job type, and status migrate as Zoho Tasks (for discrete to-do items like technician assignments) and Zoho Events (for scheduled time blocks). The Task Subject carries the job type, Due Date carries the scheduled date, and Status maps from TSP job status. TSP technician assignment resolves to a Zoho User lookup; if the technician is not a Zoho CRM user, the assignment is stored in Technician_Name__c as a text custom field pending admin review.

Trade Service Pro's custom fields — including trade type, service category, property type, contract status, and any industry-specific properties — require Zoho custom fields to be created before migration. FlitStack AI creates these as custom fields on the relevant Zoho module (Account, Contact, or Deal) matching the TSP field type. Pick-list fields use value-mapping to translate TSP values to Zoho pick-list options. Multi-select pick-lists in TSP map to Zoho multi-select pick-lists where supported; otherwise they collapse to comma-separated text.

If your Trade Service Pro setup includes non-standard modules beyond the standard customer-proposal-invoice model, FlitStack AI creates a corresponding Zoho Custom Module using Zoho's /settings/modules API. The custom module inherits your TSP field definitions as Zoho custom fields with equivalent data types, and relationship lookups to parent records are established using Zoho's lookup field type. Junction relationships (many-to-many between TSP entities) map to Zoho custom junction modules.