Migrate from Ringy (formerly iSales) to Zoho CRM

Ringy Lead is the primary record object and the only one with a documented CSV export path. We extract every Lead row and evaluate a qualification split rule during scoping to determine whether each record maps to a Zoho Lead (unqualified), a Contact attached to an Account (qualified buyer), or both. The split rule typically uses Ringy pipeline stage, any custom fields indicating qualification status, and whether the record has an associated Deal. We preserve Ringy Lead fields as custom fields on the Zoho destination for audit and reporting continuity.

Company records in Ringy export as rows within the Lead CSV export. We extract company fields (name, domain, address, phone) and normalize them into Zoho Account records. Account creation happens before Contact import so that the Account-Contact Lookup relationship is satisfied at insertion time. We use Company Name or Domain as the dedupe key during import.

Ringy Deals are associated with Leads and appear in CSV exports via filtering. Pipeline names and stage definitions migrate as Zoho Deal stage values. We preserve the pipeline-to-stage mapping as a reference document so that Zoho Deal layouts can be configured to match the original Ringy pipeline structure. Closed-won and closed-lost reasons migrate as custom fields on the Deal.

Ringy custom fields on Leads must be explicitly included via the 'Include all custom fields' checkbox during CSV export. We verify this option is selected during scoping and flag any custom fields that cannot be included in the export. Custom fields map to Zoho custom fields created either before migration (via Zoho Settings) or dynamically during import using the Migration Wizard's field creation prompt. Field type mapping (text, picklist, date, number) is verified against Zoho's supported field types during the mapping phase.

Activity records that appear in the Ringy Lead export as history entries (call disposition, email count, SMS activity) migrate to Zoho Tasks and Events. Call records with duration and disposition data become Task records with TaskSubtype=Call. Email activity becomes Event records. We preserve activity timestamps as ActivityDate to maintain timeline ordering. Note that detailed call content, call recordings, and full SMS thread bodies are not included in the Ringy CSV export and cannot be migrated.

Ringy owners referenced on Lead, Company, and Deal records are resolved by email match against Zoho User records in the destination org. Any Ringy owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes. We flag inactive Zoho Users in the destination that correspond to active Ringy users to avoid orphaned assignments.

Tags applied to Ringy records are included in the Lead CSV export where present. We extract tag values and create corresponding Tags in Zoho CRM. Tag assignment on records is preserved during import. Ringy's tag taxonomy is reviewed during scoping to ensure tag names are compatible with Zoho's tag naming conventions (no special characters beyond hyphen and underscore).

File attachments associated with Ringy Leads or Companies are not accessible via any documented export mechanism or API. We flag attachments as non-migratable and provide a manual download checklist organized by record so that the customer's admin can transfer files separately. Zoho's new WorkDrive-based attachment storage (Q1 2026 update) is referenced as the target location during this handoff.

Call history, disposition data, and call recordings are stored within Ringy's built-in VOIP softphone and activity log. There is no documented API or bulk export for call metadata or recordings. We preserve any call data that appears in the Ringy Lead CSV export rows (call count, last call date) as standard activity fields, but the full call log is not migratable. Call recordings must be exported manually from Ringy's interface if required.

Ringy drip campaigns, automated follow-up sequences, and SMS/email automation rules are platform-native automation objects with no documented export path. We document the visible campaign structure — campaign names, stages, associated templates, and timing rules — as reference metadata for the customer's admin to use when rebuilding sequences in Zoho Workflows and Blueprints post-migration. This document is delivered as part of the standard migration handoff package.

SMS message bodies and conversation threads are stored within Ringy's messaging interface and have no documented export path. Any SMS-related data that appears in the Ringy Lead CSV rows (SMS count, last SMS date) migrates as numeric and date activity fields, but full thread content cannot be extracted. We document this limitation in the migration handoff and flag it for the customer's admin if SMS thread history is a compliance or customer-service requirement.