Migrate from Xpressdocs to Mailchimp

Xpressdocs contact lists map directly to a Mailchimp Audience. We extract each contact record via the Xpressdocs Contacts/CRM API, map standard fields (email_address, first_name, last_name, phone, mailing_address) to Mailchimp's built-in EMAIL, FNAME, LNAME, PHONE, and ADDRESS merge fields, and create additional merge fields for any custom Xpressdocs contact properties. List membership in Xpressdocs translates to Mailchimp Tags or Groups depending on whether the list represents a static segment or a dynamic classification. We handle duplicate detection by email address before import to avoid creating duplicate Audience members.

Xpressdocs contact lists often carry segmentation tags indicating campaign membership, geographic region, or industry classification. We translate these into Mailchimp Groups (for mutually exclusive categories like region or industry) and Tags (for non-exclusive labels like campaign_name or buyer_persona). Groups and Tags are applied during the contact import phase so that each Audience member arrives in Mailchimp already segmented. The customer chooses the Group versus Tag strategy during scoping.

If Xpressdocs maintains a suppression list of contacts who have opted out of direct mail, we export those records and import them into Mailchimp as non-subscribed suppressions. This step is critical for email deliverability and compliance. Mailchimp counts unsubscribed contacts toward the plan limit, so the customer should decide whether to archive historical unsubscribes post-import or maintain them as a permanent suppression list.

Xpressdocs Storefronts are brand containers containing product catalogs, template libraries, and user permissions. Mailchimp has no storefront concept. We document the storefront hierarchy and active product catalogs as a written reference for the customer's admin to decide which print offerings to recreate as email content or external links. Storefront user roles (Admin, Designer, Orderer) do not map to Mailchimp audience roles; we flag these as requiring manual setup in Mailchimp's account and team management.

Xpressdocs Products represent print items (postcards, brochures, door hangers) with pricing, paper type, and coating. Mailchimp has no product catalog. We document the product list and associated pricing as a written reference. If the customer intends to use Mailchimp for promotional emails about print services, the product list serves as source material for content creation but does not migrate as structured data.

Xpressdocs Order history records fulfillment status, delivery method, line items, and recipient contacts. Mailchimp does not have an order or fulfillment object. We do not migrate historical orders. If order data is needed for re-engagement campaigns (e.g., past customers who ordered a specific product), we flag the order-to-contact association as a candidate for a custom merge field or tag so the customer's admin can build segments around purchase history.

AmazingMail triggers are rule-based direct mail campaigns tied to CRM events like service reminders, birthdays, or appointment completions. These do not migrate to Mailchimp Customer Journeys because the trigger logic (which contact receives which mailer based on which event) is platform-specific. We document each active trigger definition and its associated contact segment and deliver this as a written handoff inventory. The customer's admin uses this document to rebuild equivalent email journeys in Mailchimp.

The JSON Listing Feed API maintains agent, property, open house, and buyer/seller records in a schema separate from contacts. Mailchimp has no real estate listing object. We export the listing feed schema as a structured reference document and flag the agent-to-contact association as a merge field candidate (e.g., MOSTRECENTLISTING_ADDRESS or AGENT_LICENSE_NUMBER). The customer rebuilds listing-triggered email campaigns manually in Mailchimp using these fields as triggers or content sources.

Brand-approved logos, colors, and photography stored in Xpressdocs Custom Image Gallery are platform assets, not structured database records. We export the asset metadata and URL references. The actual image files require separate transfer via Mailchimp's Content Studio or manual upload. Brand color configurations (hex values) can be documented as a written reference for the customer's email designer to apply during template rebuild.