Migrate from Trade Service Pro to Mailchimp

Trade Service Pro customer records map 1:1 to Mailchimp subscribers. Names, emails, and phone numbers map to Mailchimp standard fields. One customer record = one subscriber in the Mailchimp audience. Additionally, any custom fields on the customer record—such as industry, service type, or account status—will be mapped to Mailchimp custom merge fields or tags, ensuring all relevant context transfers for segmentation.

Mobile phone and office phone from Trade Service Pro map to Mailchimp's PHONE merge field. Both numbers can be stored if the phone field captures mobilephone specifically. If both mobile and office numbers are present, the primary (mobile) goes in PHONE, and the secondary is stored as a custom text field (Office_Phone__c) for SMS and call reference.

Trade Service Pro location address, city, state, and ZIP are merged into Mailchimp's structured ADDRESS field (ADDR1, CITY, STATE, ZIP). Country is added as available. Addresses get stored as-is; Mailchimp does not validate deliverability. If a customer has multiple locations, the primary address is used for ADDRESS, and additional locations are stored as custom fields (e.g., Location2__c) for reference. Incomplete addresses are flagged for manual review before import.

The primary business or company name on the Trade Service Pro customer record maps to Mailchimp's COMPANY merge field. Useful for B2B segmentation and company-based campaign targeting. If a contact is linked to multiple companies, the primary company name is stored in COMPANY, while secondary affiliations are captured as custom fields (e.g., Secondary_Company__c) or tags for multi-entity segmentation. This preserves the hierarchy without duplicating subscriber records.

Work order records have no native Mailchimp equivalent. Work-order name, description, amount, and dates are encoded as custom merge fields on the subscriber record. Job status (PENDING, COMPLETED, INVOICED) maps as a tag for quick filtering. Each work order includes a reference ID stored as a custom field (Work_Order_ID__c) for traceability, and tags are applied in lowercase (pending, completed, invoiced) to match Mailchimp conventions.

Service history, technician assignments, and scheduled dates have no Mailchimp equivalent. These get encoded as custom fields (Service_History__c, Technician__c, Scheduled_Date__c) and technician names become tags for segmentation by assignment. If multiple technicians are assigned, each name is added as a separate tag for crew segmentation. Service_History__c stores a comma‑separated list of recent service types, and scheduled dates use ISO format to support time‑based automations.

Invoice totals, payment status, and due dates map to custom merge fields (Invoice_Total__c, Payment_Status__c, Due_Date__c). Payment status (PAID, UNPAID, OVERDUE) also becomes a tag so Mailchimp can filter subscribers by billing standing. If multiple invoices exist for a subscriber, the most recent total is stored in Invoice_Total__c, and the invoice date is recorded in Last_Invoice_Date__c. Historical amounts can be kept in a custom text field (Invoice_History__c) as a semicolon‑separated list.

Equipment type maps to a tag (HVAC, Plumbing, Electrical, Tree) for segment filtering. Equipment make/model and serial number are stored as custom fields for reference. This preserves field-service context for targeted re-engagement campaigns. If a subscriber has multiple equipment types, each type is added as a separate tag for segmentation. Equipment_Make_Model__c stores make and model; Equipment_Serial__c records the serial number. Tags use Title case (HVAC, Plumbing).

Any Trade Service Pro custom fields beyond standard ones get created as Mailchimp custom merge fields before import. Merge field type (text, number, date, dropdown) is set to match the source field type for accurate data display. For picklist fields, options are mirrored in Mailchimp's dropdown configuration. If a source field holds multiple values (comma‑separated), the data is stored as text and can later be split into tags for segmentation.

Trade Service Pro scheduling workflows, dispatch automations, and technician routing rules have no functional equivalent in Mailchimp. These must be rebuilt manually in Mailchimp Customer Journey builder. FlitStack exports workflow definitions as a rebuild reference. During rebuild, your team can use the exported workflow diagrams to map each trigger, condition, and action to a Mailchimp Customer Journey node. This preserves business rules in plain‑language format, reducing the learning curve.

Trade Service Pro does not primarily store email templates, but any service-related email sequences stored in the platform do not transfer. Mailchimp templates must be recreated. FlitStack can export template content if present. If you have existing HTML templates or plain‑text sequences, FlitStack will extract the content and formatting so your marketing team can re‑import them into Mailchimp's template editor. This reduces re‑creation time and preserves brand voice across transition.

Trade Service Pro reports — jobs completed, revenue by technician, outstanding invoices — have no Mailchimp equivalent. Underlying data migrates, but reporting views must be rebuilt in Mailchimp's campaign analytics. After migration, your team can use Mailchimp's analytics to track open, click, and revenue metrics. For operational metrics like jobs completed or revenue by technician, you will need to query the migrated data via Mailchimp's API or a BI tool.