Migrate from Manta Business Management Software to Mailchimp

Manta BMS Contact records map to Mailchimp Member records within a single audience. Standard fields migrate as follows: first_name maps to FNAME, last_name maps to LNAME, email maps to the email address field used as the Member unique identifier, and phone maps to a custom merge field PHONE. We run deduplication on email address before import because Mailchimp's Member model uses email as the primary key and will reject duplicate addresses. Any Manta Contact with a missing email address is held in a reconciliation queue for the customer's admin to supplement before import proceeds.

Manta BMS Company records do not map to a distinct Mailchimp object. Instead, the Company name, industry, and size attach to the Contact record via a custom merge field ORGCOMPANY (text, 255 chars) and ORGINDUSTRY (text, 255 chars). Company-contact linkage must be resolved at migration time by matching the Manta Contact's associated_company_id to the Company record and inserting the resolved company name into the merge field. Mailchimp has no relational Account-Contact model, so this flattening loses the ability to report by company in Mailchimp natively.

Manta BMS Lead records are imported as Mailchimp Members rather than a distinct Lead object, since Mailchimp has no lead management capability. We map Lead status, source, and assigned owner into merge fields LEADSTATUS and LEADSOURCE, and tag the Member with the owner name. Any Manta Lead with email_opt_in = true imports as a subscribed Member; Leads without an explicit opt-in flag are imported as pending double opt-in so that Mailchimp's re-confirmation email sequence applies before the contact receives campaigns.

Manta BMS Deals have no Mailchimp equivalent. Mailchimp tracks campaign engagement rather than pipeline stage, deal value, or expected close date. We do not migrate Deals. Instead, we export a written Deal inventory report (Deal name, value, stage, expected close date, associated Contact, and Owner) that the customer's admin retains for reference or re-entry into a CRM if the team adopts one alongside Mailchimp.

Manta BMS Activity records (calls, emails, meetings, tasks with timestamps) cannot be imported into Mailchimp as historical engagement data because Mailchimp tracks engagement only from the point of account setup forward. We do not migrate activity history. We flag the total activity count per Contact during scoping so that the customer understands the scope of data that will not appear in Mailchimp. Post-migration, Mailchimp campaign open and click data accumulates normally as the team runs email campaigns.

Manta BMS Owner records (sales reps assigned to Contacts, Leads, and Deals) have no native owner field in Mailchimp. We tag each imported Member with the owner name in the format OWNER: [Owner Name] so that the customer can create Mailchimp segments filtered by owner tag to approximate assignment visibility. Owner email addresses are preserved in a merge field OWNEREMAIL for reference. Archived or inactive Manta owners are tagged as INACTIVE: [Owner Name] and included in the reconciliation report.

Manta BMS custom field definitions are not exposed via any documented API or export format, making reliable identification and extraction of custom field data infeasible. We do not migrate custom fields. During scoping we produce a written custom field inventory listing every non-standard field found in the Manta export, the field type, and the number of records carrying a value. The customer's admin decides which custom fields to recreate as Mailchimp merge fields and populates those manually or via a follow-on import pass.

Manta BMS does not expose a documented file storage export path, and binary file handling falls outside standard CRM-to-ESP migration scope. We do not migrate attachments. Any documents or files linked to Manta Contact or Deal records are listed in the written handoff document with the original filename and record association so that the customer's admin can re-upload or link them manually in Mailchimp if supported by the customer's plan.