Migrate from Infor CloudSuite Customer Relationship Management (CRM) to Mailchimp

Infor Sales Contacts map directly to Mailchimp Subscribers as the primary migration object. Email address is the dedupe key. We deduplicate against Infor's known duplicate pool (records created by Outlook export) using email address and name matching before import. The Infor contact role (decision-maker, influencer, service contact) maps to Mailchimp Tags for segmentation. Phone number, job title, and address fields map to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS).

Infor Accounts carry company-level data (SIC code, revenue, employee count, territory) that Mailchimp cannot store as a related object. We decompose the Account into merge fields on the Subscriber: Company Name becomes a CUSTOM COMPANY merge field, SIC code and territory become tags, and revenue band becomes a custom merge field. This preserves the Account context without replicating a parent-child relationship.

Infor Leads migrate to Mailchimp Subscribers tagged with 'Lead' and optionally segmented by source (Lead source field from Infor maps to a Mailchimp Tag group). Any Infor Lead with status of Converted migrates as a Subscriber without the Lead tag. Unqualified or dormant Leads can be held in a separate Mailchimp segment pending review before full audience activation.

Infor CRM Campaigns with type, status, start/end dates, and budget migrate to Mailchimp Campaigns as a record inventory only. Campaign members (Contacts linked to an Infor Campaign) become Mailchimp tags or segments so the customer can target the same audience in Mailchimp email sends. We do not migrate campaign performance metrics (open rates, click rates) because these do not exist in Infor CRM in a transferable format.

Infor Territory assignments (sales reps linked to geographic or product regions) have no Mailchimp equivalent. We map each Territory name to a Mailchimp Tag applied to all Subscribers belonging to accounts assigned to that Territory. The customer can use these tags to build Mailchimp Segments for region-specific campaigns.

If the customer uses Infor's product catalog for e-commerce and intends to use Mailchimp's product and order sync, we migrate the Product records and Price List entries to Mailchimp Products. This is only applicable when Mailchimp is the email engine for an active e-commerce storefront. Standard CRM product records without e-commerce intent do not migrate.

Infor CRM user-defined custom fields on Contacts and Accounts (picklists, dates, lookups) map to Mailchimp Merge Fields where the field type is compatible. Picklist values become merge field options; date fields become date merge fields; lookup fields to Accounts become merge fields carrying the lookup display value. Infor-specific field types that Mailchimp cannot represent are documented in a field mapping spreadsheet for the customer to assess for manual entry or custom integration.

Infor CRM Users (sales reps assigned as record Owners) have no Mailchimp equivalent as user accounts. We optionally tag Subscribers with the Owner name as a merge field so the customer can see which rep owns the account without reconstructing the full Infor User table. Owner assignments for territory accountability are preserved in the territory tagging step.