Migrate from Ringy (formerly iSales) to Salesforce Sales Cloud

Ringy uses a single Lead object as its primary record; there is no separate Contact object. We assess each Ringy Lead at migration time to determine whether it maps to a Salesforce Lead (unqualified prospect) or a Salesforce Contact attached to an Account (qualified buyer). The split decision is based on the customer's criteria: deal stage (any stage > $0 maps to Contact), lead source, or explicit custom status field. We preserve the original Ringy Lead ID in a custom field ringy_lead_id__c on both the Lead and Contact for audit and cross-reference. Because Ringy has no API, we extract using the Generate CSV function with 'Include all custom fields' selected, and the split logic runs as a post-extraction transform before Salesforce import.

Ringy Companies are not exported via a separate documented path; company fields appear within Lead CSV rows (Company Name, Company Phone, Company Address, etc.). We normalize these fields into Salesforce Account records during the transform phase. The Account is created before any Contact or Lead import so that the AccountId lookup is satisfied at insert time. Company-level custom fields from Ringy map to custom Account fields in Salesforce.

Ringy Deals are associated with Leads and can be included in CSV exports via filtering. We extract Deal Name, Amount, Stage, Close Date, Owner, and any associated custom properties. In Salesforce, each Deal becomes an Opportunity with the StageName mapped from Ringy stage, Amount preserved, CloseDate migrated, and OwnerId resolved via email lookup against the Salesforce User table. The AccountId on Opportunity is resolved by matching the associated Lead's Company Name against the Account Name created in the prior step.

Ringy pipeline names and stage definitions are extracted as metadata during the scoping phase. We map each Ringy stage to a Salesforce StageName value within a Salesforce Sales Process that we configure before migration. Probability percentages from Ringy map to StageProbability on each Opportunity Stage entry. Stage sequence order is preserved.

Ringy's single Lead pipeline (and any custom pipeline configurations) maps to a Salesforce Record Type on Opportunity, with a corresponding Sales Process that whitelists only the relevant stage values. If the customer uses multiple pipeline configurations in Ringy, each becomes a separate Salesforce Record Type with its own Page Layout and Sales Process so stage values stay scoped per line of business.

Activity records (call disposition, email count, task history) appear in the Ringy Lead CSV export as associated history. We extract ActivityDate, ActivityType, disposition data, and notes where available. These map to Salesforce Task records: calls map with TaskSubtype=Call and CallDisposition; emails map as Task with the Ringy email body preserved in Description; tasks map with Status and Priority preserved. ActivityDate is used to maintain timeline ordering. Activity history extraction via CSV from Ringy is partial compared to API-based extraction on other platforms; we flag any gaps from the auto-audit in the scoping report.

Ringy custom fields on Lead are included via the 'Include all custom fields' checkbox in the Generate CSV export. We map each custom field to a Salesforce custom field of equivalent type (Text, Number, Date, Picklist, Checkbox) on the appropriate object. Custom field API names are normalized to Salesforce __c convention. We verify during scoping that this checkbox was used in any prior exports; if not, we request a fresh export with the option selected. Custom field metadata (field type, picklist values) is captured from Ringy's field configuration UI before the export runs.

Ringy tags applied to records appear in the Lead CSV export as comma-separated values within a tags field. We map these to Salesforce custom multi-select picklist fields on Lead or Contact. If the number of unique tags exceeds the 500-value multi-select picklist limit, we use a custom text field instead and document the full tag inventory for the customer. Tag metadata (which records had which tags) is preserved in the migration mapping document.

Ringy Owner information (Assigned To) appears in the Lead and Deal CSV export. We resolve Ringy owners by email address match against the Salesforce User table in the destination org. Any Ringy Owner without a matching Salesforce User is placed in a reconciliation queue; the customer's Salesforce admin provisions the missing User before record import resumes. Inactive Salesforce Users may be used if the customer wants to preserve historical assignment; this decision is made during scoping.

If Ringy contains standalone Company records (not tied to Leads), these export via the Lead CSV using the filter for Companies. We extract Company Name, Phone, Address, Website, and any associated custom properties, normalizing them into Salesforce Account records. Standalone Account records (without a corresponding Lead) require the customer to confirm whether these exist and whether they should be migrated as Accounts with no associated Contacts or Opportunities.

Ringy Lead Source (referral, inbound call, website, etc.) maps to the standard Salesforce Lead Source field on Lead. If Ringy uses custom source taxonomy, we map to a custom lead source field and document the mapping for the customer's reporting team.

Ringy drip campaigns are automation objects with no documented export API. We cannot migrate campaign logic, sequence timing, or branching rules. We extract visible campaign metadata from Ringy's campaign list view — campaign name, associated Lead filters, stage sequence, and template names — and deliver this as a written Campaign Rebuild Reference document. The customer's admin uses this document to rebuild drip sequences as Salesforce Flow, Engagement Paths, or Sales Engagement Cadences depending on the Salesforce edition licensed.