Migrate from Origo BPO to Mailchimp

Origo BPO exports contacts as CSV rows with name, email, phone, and account affiliation. Each row loads as a Mailchimp subscriber profile. Email address is the unique identifier — duplicate detection runs on email match against existing audience members. If the export contains multiple ticket records for the same email address, we consolidate these into a single contact profile with tags representing each associated ticket for complete history retention.

Mailchimp provides a default COMPANY merge field. Origo exported company names populate this field directly. If Origo exports split company name into separate fields, concatenation is applied before import. For organizations with complex corporate structures where contacts are affiliated with parent companies, subsidiaries, or regional offices, we can create additional merge fields to capture this hierarchy and enable segmentation by organizational unit.

Origo ticket status values (Open, In Progress, Resolved, Closed) do not map to any Mailchimp native field. We create a STATUS merge field with the exported values, and optionally apply tags like service:active or service:resolved to enable segment filtering. This dual approach allows you to filter contacts either by the STATUS merge field value or by service-related tags, providing flexibility when building segments for targeted campaigns based on ticket lifecycle stage.

Origo service categories from exported ticket data become Mailchimp tags applied per contact. Tags like billing:inquiry, support:tier1, or field:scheduled allow segmentation for targeted campaign sends without creating custom fields for every category. The tag taxonomy we develop maps directly to Origo's service type hierarchy, so your Mailchimp segments can replicate the same filtering logic used in Origo's ticket queue assignments, enabling consistent campaign targeting across the migration.

Agent names or IDs from the Origo export populate a custom AGENT merge field. This preserves the service relationship for reference and enables segment filtering by agent assignment if needed for retention or re-engagement campaigns. If your team wants to analyze contact distribution across agents or create agent-specific follow-up sequences, the AGENT field supports these use cases in Mailchimp without requiring additional data imports.

Original ticket creation timestamps from Origo export map to a date-typed merge field TICKET_DATE in Mailchimp. Date merge fields support time-based segmentation such as contacts with tickets opened in the last 90 days. This enables re-engagement campaigns targeting contacts with stale tickets or anniversary-based outreach tied to the original service request date, leveraging the historical data retained from Origo's export.

Resolution notes or last interaction text from Origo ticket records migrate to a text merge field LAST_NOTES. This is for reference only — Mailchimp's text merge fields support up to 255 characters; longer notes are truncated with a flag in the migration report.

Phone numbers from Origo contact exports populate Mailchimp's PHONE merge field. Mailchimp supports SMS marketing on Standard and Premium plans — contacts with valid phone numbers are flagged in the import report for SMS opt-in strategy planning. This allows your team to develop a coordinated email and SMS marketing approach using the contact data migrated from Origo, with phone numbers ready for SMS campaign enrollment where applicable.

If Origo exports include an opt-in flag, contacts with explicit email consent map to Subscriber status in Mailchimp. Contacts without consent or with unknown status are imported as Non-Subscribed for compliance — your team sends a re-permission campaign before activating them.

Origo ticket queues or segment assignments (e.g., Tier1-Support, VIP-Clients) are not native Mailchimp segments. We create segments in Mailchimp based on the exported queue data using tag and merge-field filter conditions — your admin defines the segment rules using our mapping document as the reference.