Migrate from Kylas Sales CRM to Mailchimp

Kylas Contact records map to Mailchimp Members within the destination Audience. We map standard fields: first_name, last_name, email, phone, address city/state/country. Email address is the required unique identifier for Mailchimp Member creation. Kylas lifecycle_stage or custom status fields map to a Mailchimp Tag (e.g., customer, prospect, inactive) if the customer wants to preserve segmentation. Opt-in and opt-out status migrates to the Member status field (subscribed, unsubscribed, pending) based on the Kylas contact's communication preference field.

Kylas Company records map to Mailchimp Company records only if the customer activates the Mailchimp e-commerce integration (requires Mailchimp Standard or Premium). Without e-commerce enabled, Companies have no direct Mailchimp equivalent and are documented in the mapping inventory as excluded. If e-commerce is active, we map company_name, industry, website, and city, and link Members to their parent Company via the Mailchimp CompanyMember association. Company-to-Contact relationships are preserved as tags on the Member (e.g., tag: CompanyName) for segmentation without requiring e-commerce.

Kylas Lead records map to Mailchimp Members with a source tag applied (e.g., tag: Lead_Source_Web, Lead_Source_Referral). Kylas lead_score and lead_source fields migrate to custom Member fields (merge fields) in Mailchimp. The customer decides whether to import all Leads or only Leads in a specific Kylas status (e.g., Open, Qualified) to avoid populating Mailchimp with unmarketable contacts. Unqualified or lost Leads are imported as unsubscribed Members or excluded entirely based on the customer's preference.

Kylas Deals have no Mailchimp structural equivalent. Mailchimp does not have a pipeline, deal stage, deal value, or probability concept. We export the full Deal inventory (deal name, stage, value, owner, expected close date) as a CSV and a written Deal Migration Document that the customer's admin can use to build a deal tracking system in a supplemental CRM, a spreadsheet, or a Mailchimp-sourced spreadsheet linked via Zapier. This is not a FlitStack AI limitation; it is a platform architecture difference.

Kylas named Pipelines with custom stage names do not map to any Mailchimp feature. We document every Pipeline and its stage names, stage order, and win/loss values in a Pipeline Configuration Inventory. The customer's admin uses this document to decide whether to rebuild pipeline tracking in a separate tool or accept that deal management is not handled in Mailchimp post-migration.

Kylas custom fields on Contact and Lead objects map to Mailchimp Merge Fields (FNAME, LNAME, EMAIL, plus customer-defined TEXT, NUMBER, DATE, PHONE, ADDRESS, or dropdown fields). We create matching Merge Fields in the destination Audience before import. Text Merge Fields in Mailchimp are hard-limited to 255 characters; any Kylas custom field with content exceeding 255 characters is flagged during pre-migration audit and truncated at 255 characters with a warning in the migration report. Dropdown or picklist fields in Kylas map to Mailchimp dropdown Merge Fields with values preserved.

Kylas tags apply across all objects (Contacts, Leads, Companies, Deals). We export the full tag vocabulary and map each tagged record to a Mailchimp Tag on the corresponding Member. Tag names are preserved verbatim, and duplicates are merged (e.g., if the same tag appears on a Contact and a Company for the same entity, it appears once on the Member in Mailchimp). Tags used exclusively on Deals or Pipelines are excluded because those records do not migrate. We deliver a Tag Taxonomy document listing all tags and their usage counts in Kylas for the admin to review before Mailchimp audience segmentation begins.

Kylas Activity records (Tasks, Calls, Notes, Meetings) attach to Leads, Contacts, Deals, and Companies but have no Mailchimp equivalent. Mailchimp tracks email engagement (opens, clicks) from the point of migration forward but does not store historical call logs, meeting records, or internal notes. We export Activities as a CSV attachment to the migration report, linking each Activity to its source Contact or Lead record by email address, so the customer's admin can reference historical interactions during outreach if needed.

Kylas User records (sales reps, admins) do not map to any Mailchimp object. Mailchimp does not have a user/owner concept for contacts. We extract the Kylas user list as a separate CSV (name, email, role, active/inactive status) for the customer's admin. If the customer uses Kylas owner assignment to route contacts, the equivalent in Mailchimp is Tag-based routing or using Mailchimp's Teams feature (available on Standard and Premium tiers) to assign audience management responsibility.

Kylas workflow automation rules (triggers, conditions, action sequences) do not export and do not have a Mailchimp equivalent as a migration target. We deliver a written Workflow Inventory documenting every active Kylas automation with its trigger event, conditions, and actions. The customer's admin reviews this document and rebuilds equivalent logic in Mailchimp Customer Journeys if applicable. Kylas automation around lead routing, stage-change triggers, or task creation cannot be replicated in Mailchimp because Mailchimp's automation is email-journey-focused.