Migrate from RSoft CRM to Mailchimp

RSoft Contact records map to Mailchimp audience members via email address as the dedupe key. Standard fields migrate: first name, last name, email, phone, address. RSoft's lifecycle stage and lead status map to Mailchimp merge fields (LIFECYCLE_STAGE, LEAD_STATUS) so that segmentation logic can be rebuilt using the same stage logic. We deduplicate on email during import and flag any duplicate email addresses with conflicting names or phone numbers for customer resolution.

RSoft Leads merge into the same Mailchimp audience as Contacts because Mailchimp has no separate Lead object. We migrate Lead email, name, phone, source, and score. The lifecycle stage on a Lead record (new, open, in_progress, unqualified) maps to the same LIFECYCLE_STAGE merge field used for Contacts, preserving the stage distinction in Mailchimp segments. The RSoft Lead-to-Contact conversion history is not portable; we document the conversion date as a note for the customer to reference manually.

RSoft Company records have no direct Mailchimp equivalent because Mailchimp has no Account or Company object. We recommend mapping company name to a COMPANY merge field on each audience member, and applying a company-based tag to every contact belonging to that company. This preserves the organizational context and allows segment filtering by company. If the customer has many companies with few contacts each, tags are the better strategy; if they have few companies with many contacts each, the merge field approach is cleaner.

RSoft Tags on Contacts, Leads, and Deals migrate as Mailchimp tags. Tags are applied to audience members during the contact import phase via batch tagging in the Mailchimp API. We deduplicate tags during import and flag any tags with identical names from different sources. RSoft tag prefixes (e.g., hot-lead, churned, referral) map directly to Mailchimp tag names without transformation.

RSoft Deals map to no Mailchimp object. Mailchimp has no Opportunity, Deal, pipeline, or stage object. We flag this gap during scoping and ask the customer to confirm they understand Deal records, stage probabilities, expected close dates, and deal amounts will not appear in Mailchimp. If pipeline tracking is required post-migration, the customer should retain a CRM license or evaluate Mailchimp integrations with Pipedrive, HubSpot, or Salesforce.

RSoft Pipeline and Stage definitions have no Mailchimp equivalent. We do not migrate pipeline stage names, stage probabilities, or stage automation triggers. These do not translate to Mailchimp's campaign and automation model. We deliver a written inventory of every active RSoft pipeline with stage names and probability percentages for the customer's admin to reference when rebuilding campaign segmentation logic.

RSoft Activities (calls, emails, meetings, tasks, notes) logged against Contacts, Leads, or Deals do not migrate to Mailchimp. Mailchimp tracks email campaign engagement (opens, clicks, unsubscribes) per audience member but does not store general CRM activity timelines. IVR call logs and autodialer records do not export via RSoft CSV and are explicitly excluded from migration scope. WhatsApp conversation threads similarly do not export via standard CSV. We identify any call recordings and WhatsApp media files for separate file transfer if retention is required.

RSoft Ticket records (with subject, status, priority, assignee, and conversation history) have no Mailchimp equivalent. Mailchimp has no support ticket or case management module. We flag this gap during scoping. If the customer uses RSoft Tickets for customer support alongside sales CRM, we recommend evaluating Help Scout, Zendesk, or Freshdesk as a replacement ticketing platform and running that migration in parallel.

RSoft Workflow definitions do not export and do not have a Mailchimp Customer Journey equivalent that can be migrated as code. We deliver a written inventory of every active RSoft workflow with its trigger conditions, filter logic, delay actions, and CRM/WhatsApp/email outcomes, plus a recommended Mailchimp Customer Journey reconstruction plan. The customer's admin rebuilds the automations in Mailchimp using the documented logic.

RSoft User and Owner records have no Mailchimp equivalent because Mailchimp is contact-centric rather than user-centric. Owner assignments on Deals, Tickets, and Activities do not map. We document the full RSoft user roster with email addresses so the customer's admin can provision Mailchimp user seats and assign admin, author, or viewer roles independently of the migrated contact data.