CRM migration

Migrate from Ringy (formerly iSales) to Freshsales

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) logo

Ringy (formerly iSales)

Source

Freshsales

Destination

Freshsales logo

Compatibility

88%

7 of 8

objects map 1:1 between Ringy (formerly iSales) and Freshsales.

Complexity

CModerate

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Ringy (formerly iSales) logo

Ringy (formerly iSales)

What's pushing teams away

  • 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.

Choosing

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Ringy (formerly iSales) objects map to Freshsales

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

maps to

Freshsales

Lead

1:1
Fully supported

Ringy 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)

maps to

Freshsales

Contact custom fields

lossy
Fully supported

Custom 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

maps to

Freshsales

Account

1:1
Fully supported

Ringy 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

maps to

Freshsales

Deal

1:1
Fully supported

Ringy 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)

maps to

Freshsales

Activity (Tasks)

1:1
Fully supported

Activity 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)

maps to

Freshsales

Contact

1:1
Fully supported

Ringy 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

maps to

Freshsales

Tag

1:1
Fully supported

Tags 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

maps to

Freshsales

User

1:1
Fully supported

Ringy 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.

Gotchas + challenges

What specifically takes care here

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) logo

Ringy (formerly iSales) gotchas

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • CSV-only extraction with manual UI steps

    Ringy has no documented public API, REST endpoint, or developer documentation for programmatic data access. Every migration relies on the 'Generate CSV' function inside the Lead export UI, which requires a logged-in user session and cannot be automated headlessly. For very large datasets, the export may need to be split by date range manually. We coordinate the export steps with the customer's Ringy admin, verify the 'Include all custom fields' checkbox is selected, and audit the resulting file before transformation begins.

  • Auto-block keywords silently filter export records

    Ringy's drip campaign system includes an auto-block feature that filters leads containing certain keywords from sequences and, in some cases, from the visible pipeline. Records that have been auto-blocked may not appear in CSV exports without explicit investigation. We audit the customer's auto-block keyword list during scoping and identify any blocked records that may have been excluded from the exported dataset. The customer then decides whether to unblock records in Ringy before re-exporting or accept the filtered dataset as the migration boundary.

  • Lead conversion field mapping must be configured before migration

    Freshsales Lead conversion maps Lead fields to Contact, Account, and Deal fields when a Lead is converted. Custom properties on Ringy Leads will be lost during conversion unless Freshsales lead conversion field mapping is configured in advance. We create the corresponding custom fields on Contact and Account before migration, then configure the Field mapping dropdown in Admin Settings > Leads Module so that each Ringy custom property persists. This configuration must be completed before the first Lead conversion occurs in production.

  • Drip campaigns and automation sequences do not export

    Ringy drip campaigns, automated follow-up sequences, and SMS/email automation rules are stored as platform-native automation objects with no documented export API. Campaign structure, sequence logic, and timing rules cannot be extracted. We document the visible campaign structure (names, stages, associated templates) as reference metadata for the customer to use when rebuilding sequences in Freshsales. Freshsales workflows and the built-in Freddy AI can partially replicate drip behavior, but the customer admin rebuilds these post-migration.

  • Call recordings and SMS message bodies are not accessible

    Call history, disposition data, and SMS conversation threads are stored within Ringy's built-in VOIP softphone and messaging interface. There is no documented export path for call recordings, call metadata, or SMS message bodies. We preserve any SMS data that appears in the Lead export's activity fields, but the actual message content and call recordings are outside the migration scope. Teams needing call recording history should retain access to Ringy read-only or download recordings manually before the migration window.

Migration approach

Six steps for a successful Ringy (formerly iSales) to Freshsales data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Ringy (formerly iSales) logo

Ringy (formerly iSales)

Source

Strengths

  • Integrated calling, SMS, and email in a single flat-rate CRM reduces tool sprawl for sales teams
  • Cloud VOIP softphone with local ID display and call scripting directly in the CRM workflow
  • Mobile app with full CRM access for field and remote sales representatives
  • Drip campaign and automated follow-up sequencing to nurture leads without manual intervention
  • Color-coded UI and straightforward navigation that reviewers consistently describe as easy to learn

Weaknesses

  • No publicly documented API — all data extraction relies on the UI-based CSV export for Leads
  • Pricing model with add-ons (power dialer, AI tools) and usage-based calling/texting creates bill shock for heavy users
  • Auto-block keyword feature silently filters leads from the pipeline without user notification
  • Performance reported as sluggish at times, particularly under high-volume usage scenarios
  • SMS thread interface is difficult to follow for teams managing high volumes of text conversations
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Moderate CRM migration. 6 of 8 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Ringy (formerly iSales) and Freshsales.

  • Object compatibility

    C

    6 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Ringy (formerly iSales): Not publicly documented.

  • Data volume sensitivity

    B

    Ringy (formerly iSales) doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Ringy (formerly iSales) to Freshsales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Ringy (formerly iSales) to Freshsales data migrations

Answers to the questions buyers ask most during Ringy (formerly iSales) to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between two and four weeks for accounts under 15,000 Leads and 3,000 Deals with straightforward custom field structures. Migrations with large custom field sets, high-volume lead databases requiring auto-block auditing, or complex Deal structures with line items move to five to eight weeks because of manual CSV extraction coordination, data quality assessment, and Freshsales lead conversion field mapping configuration. The migration timeline also depends on how quickly the customer provides Ringy export access and approves the scoping report.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Ringy (formerly iSales).
Land in Freshsales, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day