Migrate your Ringy (formerly iSales) data
Communications-first CRM with integrated calling, SMS, and email on a flat-rate pricing model. Designed for high-volume sales teams and insurance agencies that need a unified sales desk.
In its favor
Why people choose Ringy (formerly iSales)
The signal that keeps Ringy (formerly iSales) on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Low barrier to entry and fast setup — small teams and insurance agents report getting productive within days rather than weeks of initial sign-up.
Unified communications desk combines calling, SMS, and email in one interface, eliminating the need for separate tools and reducing context-switching for sales reps.
Built-in cloud VOIP softphone with local ID display directly in the CRM, which is a differentiator for teams making high volumes of outbound calls.
Color-coded UI and mobile app provide visual organization and on-the-go access that reviewers consistently describe as intuitive and easy to navigate.
Integrated drip campaign and lead nurturing automation keeps cold leads engaged without manual follow-up, saving reps significant administrative time.
Pricing opacity and unpredictable usage costs — multiple reviewers report confusion about how charges for minutes and texts accumulate beyond included allowances.
Performance slowness and sluggishness — the iSales CRM system can be slow at times according to reviewers, which impacts daily productivity for high-volume users.
Auto-blocking behavior silently filters leads from the pipeline based on keywords without clear notification to the user, causing lost prospects.
Text message threading is difficult to follow in the interface, creating confusion for teams managing high volumes of inbound and outbound SMS conversations.
No documented public API means teams with complex integration needs or large data volumes hit walls that drive them toward platforms with better developer access.
Reasons to switch
Why people leave Ringy (formerly iSales)
The recurring reasons buyers give for replacing Ringy (formerly iSales). Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Ringy (formerly iSales) fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Ringy (formerly iSales) pricing overview
Ringy uses a flat-rate base price of approximately $99 per month with add-ons including a power dialer (~$70/month) and AI response tools (~$10/month). Usage-based calling minutes and SMS messages are charged per unit once included allotments are exhausted, which creates variable monthly bills for high-volume users.
Base Plan
Tier 1 of 1
$99 per month (flat rate)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Ringy (formerly iSales)'s schedule — see our quote-based pricing →
What gets migrated
Ringy (formerly iSales) object support
Object-by-object support for Ringy (formerly iSales) migrations. Per-pair details surface during scoping.
Contacts
Mapping requiredContacts are exported via the same Lead CSV export workflow in Ringy. We extract contact-level fields including name, phone, email, and any associated custom properties. Field names may differ from the destination CRM, so we build a field mapping sheet during scoping.
Leads
Mapping requiredLeads are Ringy's primary record object 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 handle the custom fields checkbox explicitly during extraction scoping.
Companies/Accounts
Mapping requiredCompany 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 and normalize them into the destination's account object.
Deals
Mapping requiredDeals 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 the destination pipeline configuration.
Activities
Mapping requiredActivity records — calls, emails, SMS — are part of the Lead export and appear as associated history. We extract activity timestamps, types, and disposition data where available. Field names require mapping against the destination CRM's activity schema.
Custom Properties
Mapping requiredCustom fields on 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 may require transformation due to data type differences between Ringy and the destination.
Call Logs
Not in this platformCall history and disposition data are stored within Ringy's built-in VOIP softphone and CRM activity log. There is no documented API or bulk export for call recordings or detailed call metadata. We cannot migrate call logs programmatically.
SMS Threads
Not in this platformSMS content and conversation history are stored within Ringy's messaging interface. There is no documented export path for SMS threads or message bodies. We preserve any SMS data that appears in the Lead activity export but cannot guarantee full thread fidelity.
Campaigns
Not in this platformDrip campaigns and automation sequences are Ringy automation objects with no documented export API. Campaign structure, sequence logic, and timing rules cannot be extracted. We document the campaign metadata visible in the UI and flag that sequences must be rebuilt in the destination system.
Attachments
Not in this platformFile attachments associated with Leads or Companies are not accessible via any documented export mechanism or API. Attachments must be manually downloaded or migrated via a separate file-transfer process before or after the data migration.
Tags
Mapping requiredTags applied to records exist in Ringy and may appear in the CSV export depending on how the record was structured. There is no dedicated tag export. We extract tag values from the Lead CSV rows where present and map them to the destination's tagging or labeling system.
| Object | Support | Notes |
|---|---|---|
| Contacts | Mapping required | Contacts are exported via the same Lead CSV export workflow in Ringy. We extract contact-level fields including name, phone, email, and any associated custom properties. Field names may differ from the destination CRM, so we build a field mapping sheet during scoping. |
| Leads | Mapping required | Leads are Ringy's primary record object 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 handle the custom fields checkbox explicitly during extraction scoping. |
| Companies/Accounts | Mapping required | 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 and normalize them into the destination's account object. |
| Deals | Mapping required | 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 the destination pipeline configuration. |
| Activities | Mapping required | Activity records — calls, emails, SMS — are part of the Lead export and appear as associated history. We extract activity timestamps, types, and disposition data where available. Field names require mapping against the destination CRM's activity schema. |
| Custom Properties | Mapping required | Custom fields on 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 may require transformation due to data type differences between Ringy and the destination. |
| Call Logs | Not in this platform | Call history and disposition data are stored within Ringy's built-in VOIP softphone and CRM activity log. There is no documented API or bulk export for call recordings or detailed call metadata. We cannot migrate call logs programmatically. |
| SMS Threads | Not in this platform | SMS content and conversation history are stored within Ringy's messaging interface. There is no documented export path for SMS threads or message bodies. We preserve any SMS data that appears in the Lead activity export but cannot guarantee full thread fidelity. |
| Campaigns | Not in this platform | Drip campaigns and automation sequences are Ringy automation objects with no documented export API. Campaign structure, sequence logic, and timing rules cannot be extracted. We document the campaign metadata visible in the UI and flag that sequences must be rebuilt in the destination system. |
| Attachments | Not in this platform | File attachments associated with Leads or Companies are not accessible via any documented export mechanism or API. Attachments must be manually downloaded or migrated via a separate file-transfer process before or after the data migration. |
| Tags | Mapping required | Tags applied to records exist in Ringy and may appear in the CSV export depending on how the record was structured. There is no dedicated tag export. We extract tag values from the Lead CSV rows where present and map them to the destination's tagging or labeling system. |
Gotchas
What to watch for in Ringy (formerly iSales) migrations
Issues we've hit on past Ringy (formerly iSales) migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| High | Usage-based billing for calling and texting is not obvious |
| High | No public API — all data extraction is CSV-only via the UI |
| Medium | Auto-block keyword feature silently filters records from exports |
| Medium | Drip campaign and automation logic cannot be exported |
Leaving Ringy (formerly iSales)?
Where Ringy (formerly iSales) customers move next
12 destinations Ringy (formerly iSales) can migrate to.
How a Ringy (formerly iSales) migration works
Four steps, Ringy (formerly iSales)-specific
Connect
Not publicly documented into Ringy (formerly iSales). Scopes limited to read-only on the data we move.
Map
We translate Ringy (formerly iSales)-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Ringy (formerly iSales) quirks before production.
Migrate
Full migration with Ringy (formerly iSales) rate-limit handling. Rollback available throughout.
FAQ
Ringy (formerly iSales) migration FAQ
Answers to the questions buyers ask most during Ringy (formerly iSales) migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Ringy (formerly iSales) migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Ringy (formerly iSales).
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Ringy (formerly iSales) setup and destination — written quote back within a business day.