Migrate from Ringy (formerly iSales) to Mailchimp

Ringy Leads are the primary migration record. We export via the UI CSV function with the Include all custom fields checkbox explicitly selected. Standard fields map directly: first_name, last_name, email, phone. The lead's status, source, and any sales rep assignment migrate as Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE plus custom fields like LSOURCE and SALESREP). We resolve any duplicate email addresses against existing Mailchimp audience members before import to avoid creating duplicate profiles.

Ringy Company records are associated with Leads but have no separate export path. We extract the company name and any company-level fields from the Lead CSV rows where they appear. Company data migrates to Mailchimp COMPANY merge field on the Member record, or is stored as a custom merge field if the customer prefers a normalized company object structure. Multiple Leads from the same company will share the same company value unless the customer requests company-level deduplication into a single group.

Deals in Ringy track pipeline stage, value, and expected close date against a Lead. Mailchimp has no opportunity or pipeline object. We export Deal records as a separate reference CSV documenting Lead ID, Deal name, stage, value, and close date. The customer uses this as a rebuild reference in a dedicated CRM tool if deal tracking continues to be required. Deals are not imported into Mailchimp as a data object.

Ringy activity records — call logs, email timestamps, and SMS threads — appear as associated history on Lead records in the CRM. Mailchimp does not store call or SMS history. Call duration, disposition, and timestamp data is exported as a reference CSV and preserved as metadata alongside the contact record. Actual engagement history (opens, clicks, unsubscribes) in Mailchimp begins from the date of first campaign send post-migration.

Ringy custom fields on Leads must be explicitly included in the CSV export via the Include all custom fields checkbox. We map each custom field to a Mailchimp merge field of appropriate type: text fields to text merge fields, date fields to date merge fields, numeric fields to number merge fields, and checkbox or multi-select fields to either text merge fields or tag assignments depending on the field cardinality. Mailchimp allows up to 40 merge fields per audience, which covers most Ringy custom field sets.

Tags applied to Ringy Leads are extracted from the CSV export where they appear in the record row. Tags map directly to Mailchimp Tags on the corresponding Member record. Tag names are normalized to remove special characters that Mailchimp does not accept. If the same tag applies to multiple Leads, it becomes a Mailchimp Tag with multiple Member assignments, enabling the customer to build Mailchimp segments from migrated tag data.

Ringy drip campaigns and automated follow-up sequences are platform-native automation objects with no documented export API. We do not migrate campaigns as functional objects. We deliver a written campaign inventory documenting campaign names, associated templates, stage sequences, and timing rules for the customer to use as a reference when rebuilding in Mailchimp Customer Journeys. The inventory is organized by campaign so the rebuild scope is clear.

Ringy stores call recordings and detailed call metadata within its built-in VOIP softphone and activity log. There is no documented bulk export path for call recordings or call disposition data. Call history does not migrate to Mailchimp. We export any call disposition and timestamp data that appears in the Lead CSV export as a reference CSV, but call recordings and audio files require a separate file-transfer process outside standard migration scope.