Migrate from Jobsite Mobile to Mailchimp

Every Jobsite Mobile contact record becomes a Mailchimp audience member. Email address serves as the unique key — contacts without a valid email address cannot import into Mailchimp and are flagged separately for manual resolution before the bulk import runs. We validate email format during the pre-migration scan to identify problematic addresses early.

Jobsite Mobile company records do not have a direct Mailchimp equivalent. Company name and billing address migrate as Mailchimp merge fields (COMPANYNAME, BUSINESSADDRESS) on each contact, preserving the business context from Jobsite without requiring a separate object in Mailchimp. If a contact has no associated company record, the merge fields remain empty but do not block import.

Jobsite Mobile stores trade type, service territory, equipment installed, and contract status as custom properties on contacts. Each unique property becomes a Mailchimp merge tag (Fieldequip, Territory, Contracttype) scoped to your audience. Mailchimp allows up to 40 merge tags per audience — we map the first 40 and surface overflow fields as a separate reference export.

Work orders, service tickets, job statuses, and line items in Jobsite Mobile have no Mailchimp analogue. These records do not migrate. We export a work-order summary as a CSV reference file your team can keep for record-keeping, but Mailchimp contacts will not carry job history in the platform natively.

Jobsite Mobile service notes attached to contacts import as Mailchimp notes on the contact record (limited to 1,000 characters per note). Longer or multi-entry history surfaces as a CSV export linked by contact email. If note volume per contact is high, we can alternatively create tagged entries (e.g., TAG: ServiceNote_2024-03) for easier segmentation in Mailchimp.

If Jobsite Mobile supports labeling or tagging contacts (e.g., 'VIP Customer', 'HVAC Only'), those labels migrate directly as Mailchimp tags. Tags are additive — a contact can have multiple tags from Jobsite Mobile. Mailchimp tags are case-sensitive; we normalize all imported tags to title-case during migration.

Jobsite Mobile assigns a technician or owner to each job. This relationship (which technician last served a customer) can become a Mailchimp segment filter or a tag (e.g., 'LastServicedBy: MikeR') so you can target customers by service representative in Mailchimp campaigns. We offer both options and let you choose before migration runs.

Photos and documents attached to Jobsite Mobile work orders or contact records do not migrate to Mailchimp. Mailchimp is an email marketing platform and does not store file attachments on contact records. We export attachment metadata (file name, linked contact email, Jobsite URL if available) as a reference CSV your team can keep alongside Mailchimp data.

Jobsite Mobile may track email consent or do-not-contact flags. We map these to Mailchimp's contact status: opted-in contacts become 'subscribed', explicitly unsubscribed contacts import as 'unsubscribed' (and suppress in Mailchimp), and bounced or invalid addresses import as 'cleaned'. Any contacts with unknown consent status flag for your review before import.

We store the original Jobsite Mobile record ID as a custom merge field (JOBSITE_ID__c equivalent in Mailchimp merge tag format) on each contact. This allows you to cross-reference Mailchimp contacts back to Jobsite Mobile records and supports delta-reconciliation if you run a follow-up sync after the initial migration.

Jobsite Mobile timestamps (created date and last-modified date) for each contact record preserve as Mailchimp merge fields. Mailchimp's native 'Member Since' date reflects the migration import date, not the original customer record date. Custom timestamp fields maintain historical continuity for segmentation and reporting in Mailchimp.

If Jobsite Mobile stores parent-company and subsidiary relationships, these map as a flat company name in Mailchimp's address and company merge fields. The hierarchy relationship is preserved as a tag (e.g., 'SubsidiaryOf: AcmeCorp') for segmentation rather than a native linking structure, since Mailchimp does not support multi-level organizational hierarchies.