Migrate from Ringy (formerly iSales) to Twenty CRM

Ringy's Lead is the primary record object and the only object with a documented CSV export path. We extract all Lead fields including name, phone, email, address, and custom properties via the 'Include all custom fields' checkbox. The Lead CSV rows map directly to Twenty People records. We use email as the dedupe key. Any Lead without an email address is held in a reconciliation queue and imported as a People record with a manual-email flag set.

Company data in Ringy appears as inline fields within Lead export rows rather than as a separate object. If a Ringy Lead has a populated company name, we extract it and create a Twenty Company record, then link the People record to that Company via the WorkWith field. Multiple Leads with the same company name resolve to a single Twenty Company record.

Ringy Deals are associated with Leads and appear in the Lead CSV export when Deal filtering is applied. Each Deal maps to a Twenty Opportunity. We pre-create the Opportunity in Twenty with the linked People as the Contact and the Company as the AccountWorkedOn. Pipeline stage names from Ringy migrate as Opportunity stage values in Twenty.

Ringy deal stages (e.g., New, Contacted, Proposal, Won, Lost) map to Twenty Opportunity stage values. We capture the stage names from Ringy's pipeline configuration during discovery and create the corresponding stage values in Twenty before any Opportunity import begins.

Call disposition data attached to a Lead in Ringy migrates to a Twenty Note linked to the People record. Ringy stores call metadata (date, duration, disposition) as activity history within the Lead record. We extract these as structured Note records with a call-type tag for timeline visibility. Detailed call logs and recording URLs are not available via Ringy's export and do not migrate.

Email activity history attached to a Lead in Ringy migrates to a Twenty Note record linked to the People record. We preserve the email timestamp, subject, and body content. Email engagement metadata (opens, clicks) that lives in Ringy's drip analytics is not available via export and does not migrate.

SMS activity that appears in the Lead activity timeline migrates as a Note record with an sms tag. The full SMS conversation thread content is not available via Ringy's export and does not migrate as threaded conversation history.

Ringy custom fields on Leads must be explicitly included via the 'Include all custom fields' checkbox during export. We map each custom field to a corresponding Twenty custom field, pre-creating the field in Twenty Settings → Data Model before import. Custom field data types (text, number, date, picklist) require mapping to Twenty's supported field types. Any custom field not included in the export checkbox is not recoverable after extraction.

Tags applied to Ringy Lead records are extracted from the CSV export rows where present. Tags migrate to Twenty as multi-select picklist fields on the People object. The customer chooses which tag taxonomy maps to which field during scoping.

Ringy Owner email addresses are extracted from Lead, Company, and Deal records. We match by email against Twenty workspace Members. Owners without a matching Twenty User are held in a reconciliation queue. The customer provisions any missing Twenty users before record import resumes because OwnerId references are required on Opportunity and People records.