Migrate from Livespace CRM to Mailchimp

Account tier verification and API scoping

We confirm that the Livespace account is on the Automation plan or above (required for API access) and validate the API credentials. If the account is on Base tier, we redirect the customer to Livespace's manual export tool and handle Mailchimp-side import from the exported CSV only. We call the Get custom fields endpoint to retrieve the full Person, Company, and Deal schema, and identify any hidden or required fields that will affect the import pipeline. We also pull the Get contact group list to inventory all static segments before planning the tag mapping.

Mailchimp audience preparation and merge field design

We create the Mailchimp audience (or identify the existing target audience) and configure the merge fields required for the Livespace data. Standard merge fields (FNAME, LNAME, PHONE, ADDRESS) are added if not already present. Custom merge fields (COMPANY, LEADSOURCE, LIFECYCLESTAGE) are created via Mailchimp's API with appropriate types (text, date, number). We define the tag naming convention for Contact Groups and agree on it with the customer before migration begins. Any Mailchimp audience-level required fields are identified so they can be populated or made optional before Person import starts.

Company resolution and denormalization

We extract all Livespace Company records and resolve each unique company name. For each Person record, we look up the associated Company and denormalize the company name onto the subscriber record as the COMPANY merge field value. If Livespace companies have parent-subsidiary hierarchies, we encode the structure as nested tags or as structured text in a custom merge field. The resolved Person-to-Company mapping is written into the import payload so company data is present on the subscriber record at the point of insert.

Contact import with duplicate and error handling

We import Persons as Mailchimp subscribers in batches using the Mailchimp Members API. Email address is the dedupe key — we set the Mailchimp status by mapping Livespace's contact status (active, inactive, bounced). Records with duplicate emails are flagged and held in a reconciliation queue for the customer to review. We apply Contact Group memberships as Mailchimp tags in the same pass. Invalid emails (format failures) are logged separately and reported post-migration. Livespace's custom Person fields are mapped to the corresponding Mailchimp merge fields as text or number values.

Post-import reconciliation and source attribution

We run a row-count reconciliation comparing the number of Livespace Person records imported to Mailchimp subscribers created, and report on the counts of added, updated, duplicate, and invalid records. Source values from Livespace are applied as tags or LEADSOURCE merge field values. We validate that each Contact Group's membership is reflected in the corresponding Mailchimp tag counts. The customer receives a migration summary with record counts, error logs, and a list of records that require manual review.

Written handoff for non-migratable objects and automation rebuild

We deliver a written document that inventories every Livespace Deal (stage, value, owner, associated Person), Space (pipeline structure, stage values, deal counts), open Task (assignee, status, due date, body), and Email Sequence (step count, trigger, cadence type, associated audience). This document is the customer's blueprint for manual rebuild in Mailchimp's Customer Journey builder or for planning a dual-stack setup with a lightweight CRM. We do not rebuild sequences, workflows, or automations as part of this migration scope.