Migrate from Ringy (formerly iSales) to Nutshell

Ringy's Lead object is the primary record and the only object with a documented CSV export path. The UI's 'Generate CSV' function supports filtering and an 'Include all custom fields' checkbox. We extract all Ringy Lead fields and map them to Nutshell Lead fields including name, phone, email, address, status, and source. Any custom properties on Ringy Leads require explicit inclusion via the checkbox and are mapped to Nutshell custom fields that we pre-create in the destination account during schema setup.

Ringy Contacts are exported via the same Lead CSV export workflow. We extract contact-level fields including name, phone, email, and any associated custom properties. Ringy does not have a separate Contact object — contact records live within the Lead export and are identified by record type or tag fields. We separate Ringy Leads into Nutshell Leads and People based on qualification status flags visible in the export data.

Company records exist in Ringy and can be filtered in the Leads export. There is no separate documented export path for Companies. We extract company fields from Lead rows (company name, domain, address, industry) and normalize them into Nutshell Company records. Company-to-Lead linkage in Nutshell is resolved via the lookup relationship after both objects are created.

Deals in Ringy are associated with Leads and can be included in CSV exports via filtering. Pipeline names and stage definitions are preserved as metadata during extraction and mapped to Nutshell Deal stages. We pre-create Nutshell pipeline configurations to match the Ringy pipeline structure before migration begins. Deal values, close dates, and stage history migrate as standard Deal fields.

Activity records — calls, emails, SMS — appear as associated history within the Lead export. We extract activity timestamps, types, and disposition data where available. Note that detailed call logs and SMS message bodies are not guaranteed in the CSV export and are flagged as partial in the migration scope. Nutshell Activities are linked to the parent Lead or People record via the activity's record reference.

Custom fields on Ringy Leads must be explicitly included during CSV export via the 'Include all custom fields' checkbox. We verify this option is selected during extraction scoping and flag any custom fields that appear to be missing from the exported dataset. Nutshell custom fields for Leads, People, and Companies are pre-created during schema setup with matching field types (text, long text, currency, date, dropdown) per Nutshell's custom field configuration.

Tags applied to Ringy records exist in the CSV export and are extracted as pipe-delimited or comma-separated values per record. We map these to Nutshell Tags on the corresponding Lead or People record. There is no dedicated tag export in Ringy — tag values are embedded in the Lead row and require parsing during the transform phase.

Drip campaigns and automation sequences in Ringy are platform-native objects with no documented export API. We document the visible campaign structure — names, stages, associated templates, and sequence order — as reference metadata for the customer to use when rebuilding in Nutshell. The customer or a Nutshell automation specialist rebuilds drip sequences post-migration using Nutshell's email automation tools or a third-party sales engagement platform.