CRM migration
Field-level mapping, validation, and rollback between Ringy (formerly iSales) and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Ringy (formerly iSales)
Source
Freshsales
Destination
Compatibility
7 of 8
objects map 1:1 between Ringy (formerly iSales) and Freshsales.
Complexity
CModerate
Timeline
2-4 weeks
Overview
Moving from Ringy (formerly iSales) to Freshsales is a CSV-based migration constrained by Ringy's lack of a public API. All data extraction relies on the UI-based Generate CSV function, which requires a logged-in session and cannot be automated headlessly. We audit the auto-block keyword list during scoping to identify any records that may have been silently filtered before export, extract with custom fields explicitly included, and load into Freshsales via CSV import with lead conversion field mapping configured so that custom property values survive the Lead-to-Contact convert. Drip campaigns, automation sequences, call logs, and SMS threads do not migrate; we deliver a written inventory of Ringy campaign structure for the customer's admin to rebuild in Freshsales.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Ringy (formerly iSales) object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Ringy (formerly iSales)
Lead
Freshsales
Lead
1:1Ringy Leads map directly to Freshsales Leads. The CSV export uses the 'Generate CSV' function with 'Include all custom fields' selected. We extract all standard fields (name, phone, email, address) plus any custom properties added by the customer. Auto-block filtered records are identified during scoping by auditing the keyword list and comparing against the full lead set before export. Lead source and status fields map to Freshsales lead_status and lead_source with custom field creation for any non-standard Ringy values.
Ringy (formerly iSales)
Lead (custom properties)
Freshsales
Contact custom fields
lossyCustom properties on Ringy Leads require explicit mapping through Freshsales lead conversion field configuration before migration. We create matching custom fields on Freshsales Contact during setup, then configure the Field mapping dropdown in Admin Settings > Leads Module so that each Lead custom field maps to its corresponding Contact custom field. This ensures that when Leads convert to Contacts, custom property values are preserved rather than lost.
Ringy (formerly iSales)
Company
Freshsales
Account
1:1Ringy Company records are extracted through the Lead export with company data embedded in Lead rows. We normalize company data into Freshsales Account records. Company name becomes the Account name, domain extracted from email addresses populates the Website field, and physical address fields map to the billing address on Account. We use company name as the dedupe key during import to prevent duplicate Account creation.
Ringy (formerly iSales)
Deal
Freshsales
Deal
1:1Ringy Deals associated with Leads are included in CSV exports via filtering. Pipeline names and stage definitions are extracted as metadata and mapped to Freshsales deal stage values. The deal amount, close date, and owner assignment migrate directly. We configure Freshsales deal stages to match Ringy pipeline stages before import so that stage assignment is valid at insert time.
Ringy (formerly iSales)
Activity (call, email, SMS)
Freshsales
Activity (Tasks)
1:1Activity records appearing in Ringy's Lead export (call dispositions, email timestamps, SMS references) migrate to Freshsales Tasks. Call activity maps with TaskSubtype = Call, duration fields map to custom Task fields, and disposition values map to custom picklist fields. We preserve activity timestamps to maintain the chronological timeline. Note that detailed call recordings and SMS message bodies do not export from Ringy and are not included in the migration scope.
Ringy (formerly iSales)
Contact (from Lead export)
Freshsales
Contact
1:1Ringy Contacts are extracted via the same Lead CSV export workflow. We extract contact-level fields including name, phone, email, and any associated custom properties. After mapping to Freshsales Lead during the initial import phase, we create a parallel Contact record where the customer has already performed Lead conversion or where the contact data warrants a separate Contact record. Contact creation happens after Account creation to satisfy lookup requirements.
Ringy (formerly iSales)
Tag
Freshsales
Tag
1:1Tags applied to Ringy records exist in the CSV export and migrate to Freshsales tags. We extract tag values from Lead CSV rows and import them as Freshsales tag entries. Tag values that do not yet exist in Freshsales are created during import. Tags serve as a lightweight segmentation mechanism and do not require custom field configuration.
Ringy (formerly iSales)
Owner
Freshsales
User
1:1Ringy Owners referenced on Lead, Deal, and Activity records map to Freshsales Users. We resolve owners by email match. Any Ringy Owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner resolution is required before Deals and Activities can reference the correct User.
| Ringy (formerly iSales) | Freshsales | Compatibility | |
|---|---|---|---|
| Lead | Lead1:1 | Fully supported | |
| Lead (custom properties) | Contact custom fieldslossy | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Activity (call, email, SMS) | Activity (Tasks)1:1 | Fully supported | |
| Contact (from Lead export) | Contact1:1 | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| Owner | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Ringy (formerly iSales) gotchas
Usage-based billing for calling and texting is not obvious
No public API — all data extraction is CSV-only via the UI
Auto-block keyword feature silently filters records from exports
Drip campaign and automation logic cannot be exported
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Scoping and auto-block audit
We audit the customer's Ringy account for data volume (Lead count, Deal count, activity records), custom field definitions, pipeline and stage names, and owner assignments. We specifically audit the auto-block keyword list to identify any records that may have been silently filtered from the exportable dataset. We document the findings in a written scoping report that includes the export strategy, any records excluded by auto-block, and the list of custom fields to create in Freshsales before import.
Freshsales schema preparation
We configure the Freshsales destination account before any data loads. This includes creating custom fields on Lead, Contact, and Account to match Ringy custom properties, configuring lead conversion field mapping in Admin Settings, setting up deal stages and pipelines to match Ringy pipeline structure, and provisioning User records that match Ringy owners by email. Schema configuration happens in a Freshsales trial or sandbox environment first for validation before production migration.
CSV export coordination
We coordinate the Ringy CSV export with the customer's admin. We verify that 'Include all custom fields' is selected in the Generate CSV function, confirm the date range covers all active and recent records, and download the resulting file. For large datasets, we may split the export into multiple files by date range or by pipeline. We validate the file row count and column headers against the scoping report before transformation begins.
Data transformation and field mapping
We transform the Ringy CSV into Freshsales CSV format with correct field names, valid picklist values, and properly formatted dates and phone numbers. We resolve owner email addresses to Freshsales User IDs, map company names to Account records, and split Deal data into the correct Freshsales deal format. Custom field values are mapped to the corresponding Freshsales custom fields created during schema preparation. We run a test import with a sample of 50-100 records to validate mapping before full production import.
Production import and reconciliation
We execute the production CSV import into Freshsales using the platform's native import wizard. We run record-count reconciliation comparing the Ringy export row count to the Freshsales import success count, investigate any rejected records, and correct mapping errors. Activities are imported after Leads, Contacts, Accounts, and Deals to satisfy lookup requirements. We deliver a reconciliation report showing record counts by object and any records that could not be imported with the error reason.
Campaign inventory handoff and cutover
We deliver a written inventory of Ringy drip campaigns and automation sequences documenting campaign names, stages, associated templates, and timing rules. This serves as the reference document for the customer's admin to rebuild sequences in Freshsales Workflows. We do not rebuild campaigns as code. During cutover, we freeze writes to Ringy, run a final delta import of any records modified during the migration window, and confirm Freshsales is the system of record. We support a 48-hour hypercare window for reconciliation issues.
Platform deep dives
Ringy (formerly iSales)
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 6 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Ringy (formerly iSales) and Freshsales.
Object compatibility
6 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Ringy (formerly iSales): Not publicly documented.
Data volume sensitivity
Ringy (formerly iSales) doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Ringy (formerly iSales) to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Ringy (formerly iSales) to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Ringy (formerly iSales)
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.