Migrate from StrategicERP to Mailchimp

StrategicERP Contact records map directly to Mailchimp subscribers within a target Audience. The email address field is the unique key — Mailchimp enforces one subscriber record per email per Audience, so contacts with duplicate emails across projects collapse into a single subscriber.

Standard name fields map to Mailchimp's built-in FNAME and LNAME merge variables. These drive personalization tokens in subject lines and email body copy. Empty or null names are preserved as blank merge values — no default substitution applied for each subscriber.

The email address is the primary key for the Mailchimp subscriber record. FlitStack validates email format before import and flags malformed addresses (missing @, invalid domain) in the pre-migration data quality report. Hard bounces are suppressed before import to protect sender reputation.

Mailchimp's Essentials and Standard plans do not include a native PHONE merge field — it must be created as a custom merge field before import. We create PHONE__c-style field (named PHONE in Mailchimp's UI) during the Mailchimp schema setup step and map the source phone value to it.

StrategicERP contacts carry a company name or company_id foreign key. We resolve the company name from the Company table and map it to a COMPANY merge field on the subscriber. As a secondary treatment, we also create an audience tag per unique company name so you can segment by company within Mailchimp without a custom field.

Mailchimp has no standalone Company object. Each unique company name from StrategicERP becomes an audience tag (enabling segment-based filtering). Company-level fields that don't fit the subscriber model (industry, annual revenue, number of employees) map as additional merge fields on the contact record — your team decides which company attributes to include based on Mailchimp's merge field limit.

Mailchimp's ADDRESS merge field is a structured field (addr1, addr2, city, state, zip, country). We parse StrategicERP's address components — street, city, state, postal code, country — into the correct ADDRESS merge field subfields. If StrategicERP stores address as a single free-text field, we parse it using a best-effort tokenizer and flag ambiguous records.

The StrategicERP internal record ID is preserved as a custom merge field on the Mailchimp subscriber for traceability. This allows your team to cross-reference any Mailchimp subscriber back to the original StrategicERP contact record and supports delta-run de-duplication on subsequent imports.

StrategicERP project records (project name, phase, status, budget, milestones) have no Mailchimp equivalent. Projects do not map to subscribers, tags, or any Mailchimp object. We include the project-to-contact linkage as a custom merge field (PROJECT_NAME or PROJECT_ID) if your team wants to tag subscribers by their associated project — this is a manual decision point before migration runs.

Invoice amounts, payment status, purchase order lines, and billing addresses stored in StrategicERP are ERP-domain transactional data. Mailchimp has no invoice or financial record concept. Those records remain in StrategicERP as the system of record. Mailchimp's e-commerce integration requires Shopify or WooCommerce as the system of record — not a construction ERP.

StrategicERP custom objects (Enterprise tier) — such as Unit, Plot, Buyer, or Inspection — map to Mailchimp as either additional merge fields on the subscriber or as named audience tags. The mapping approach depends on the custom object's cardinality: 1:1 objects become merge fields, N:N objects become tags. We surface the full custom object list in the pre-migration discovery call.

Documents, drawings, photos, and PDFs attached to StrategicERP contacts, companies, or projects cannot migrate to Mailchimp. Mailchimp has no attachment storage. We recommend exporting the full attachment manifest from StrategicERP (file names, download URLs, associated record IDs) as a CSV reference file so your team can manually relink files in whatever document management tool they adopt.