CRM migration

Migrate from Ringy (formerly iSales) to monday CRM

Field-level mapping, validation, and rollback between Ringy (formerly iSales) and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.

Ringy (formerly iSales) logo

Ringy (formerly iSales)

Source

monday CRM

Destination

monday CRM logo

Compatibility

75%

6 of 8

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

Complexity

CModerate

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Ringy (formerly iSales) has no public API, so every migration relies on the CSV export inside the Ringy UI. We extract Leads with the 'Include all custom fields' checkbox enabled, audit the auto-block keyword list to identify silently filtered records, and map the resulting rows into Monday.com's People (Contacts), Companies, and Deals boards. Monday.com's board-based data model means Ringy pipeline stages map to board columns and statuses, while drip campaign logic and automation sequences cannot be exported and are documented for rebuild in Monday.com's Automation Center. Activity history (calls, emails, SMS) that appears in Ringy's Lead export rows migrates to Monday.com's Activity timeline. Call recordings, SMS thread bodies, and file attachments do not have an extraction path from Ringy and are noted as out-of-scope. We use Monday.com's API for all destination writes with batch chunking and rate-limit handling.

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

monday CRM logo

monday CRM

What's pulling them in

  • Users praise the board-based visual interface for making pipeline stages immediately legible to non-technical team members without CRM training.
  • The no-code automation builder lets sales ops teams create lead routing, stage updates, and email triggers without developer involvement.
  • Integration ecosystem connects to Slack, Gmail, Outlook, and Zapier with minimal configuration, reducing friction for teams already using these tools.
  • The flexible column system lets teams build custom CRM views — deal value, close date, lead source — without needing a developer or pre-defined schema.
  • Teams already using monday Work Management can layer CRM features onto existing boards rather than starting from scratch.

Object mapping

How Ringy (formerly iSales) objects map to monday CRM

Each row shows how a Ringy (formerly iSales) object lands in monday CRM, 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

monday CRM

Person (Contact)

1:1
Fully supported

Ringy Leads are the primary record object and the only object with a documented CSV export path. We extract via the UI-based 'Generate CSV' function with the 'Include all custom fields' checkbox explicitly enabled. The resulting rows map to Monday.com People (Contacts) records. First name, last name, email, phone, and any custom fields extracted from the CSV are mapped to Monday.com Person column types. We deduplicate by email address before insert to prevent duplicate Person records in Monday.com.

Ringy (formerly iSales)

Contact

maps to

monday CRM

Person (Contact)

1:1
Fully supported

Ringy Contacts exist as a separate object type but export via the same Lead CSV workflow in Ringy. We extract contact-level fields alongside Lead rows and normalize them into Monday.com People. If Contacts and Leads share the same email address, we consolidate into a single Person record. Tag values attached to the Contact in Ringy migrate to Monday.com Tags on the Person record.

Ringy (formerly iSales)

Company

maps to

monday CRM

Company

1:1
Fully supported

Company records in Ringy can be filtered in the Lead CSV export and appear as associated data on Lead rows. We extract company name, domain, address, and any company-level custom fields and normalize them into Monday.com Company records. Monday.com Companies link to People (Contacts) via the relationship column. If no company data exists in Ringy for a given Contact row, we create a placeholder Company record with the domain parsed from the contact's email address.

Ringy (formerly iSales)

Deal

maps to

monday CRM

Deal (board Item)

1:1
Fully supported

Ringy Deals are associated with Leads and can be included in CSV exports via filtering. Deal name, amount, stage, close date, and owner map to Monday.com Deal board Items with corresponding column values. We preserve the pipeline name as a board label and stage names as status column values on the Deal board. Owner assignment resolves via email match to Monday.com Team Members.

Ringy (formerly iSales)

Deal Stage

maps to

monday CRM

Status Column

lossy
Fully supported

Ringy pipeline stage definitions are preserved as metadata during extraction and mapped to Monday.com Status column options on the Deals board. Each Ringy pipeline maps to a separate Monday.com CRM Deals board or a separate group within a single Deals board, depending on the customer's preferred structure. Stage probabilities from Ringy are noted in the documentation but are set manually in Monday.com as there is no native probability field.

Ringy (formerly iSales)

Activity

maps to

monday CRM

Activity (Emails & Activities)

1:1
Fully supported

Activity records — calls, emails, and SMS — appear in Ringy's Lead export as associated history rows. We extract activity timestamps, activity type, disposition data, and notes where available from the CSV rows. Activity type maps to the Monday.com Activity sub-type (call, email, meeting). Activity content and notes migrate to Monday.com Activity records linked to the corresponding Person (Contact) record. We preserve activity ordering by timestamp to maintain the Person's activity timeline.

Ringy (formerly iSales)

Custom Properties

maps to

monday CRM

Custom Columns

lossy
Mapping required

Ringy custom fields on Leads must be explicitly included via the 'Include all custom fields' checkbox during CSV export. We map each Ringy custom field to the closest Monday.com column type: text fields map to Text columns, numeric fields to Number columns, date fields to Date columns, and multi-value fields to List columns. If a Ringy custom field contains a value set, we create a corresponding List option in Monday.com. Any dependency relationships between Ringy custom fields are documented as Monday.com Column Dependencies for manual configuration.

Ringy (formerly iSales)

Tag

maps to

monday CRM

Tag

1:1
Fully supported

Tags applied to records in Ringy appear in the CSV export depending on how the record was structured. We extract tag values from Lead and Contact rows and apply them as Tags on the corresponding Monday.com Person record. Tag-based segmentation in Ringy maps to Monday.com Tag filtering in board views.

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

monday CRM logo

monday CRM gotchas

High

Subitems are not included in bulk exports

High

Daily API call limits vary sharply by plan

Medium

Legacy automations (Sentence Builder) are being deprecated

Medium

Excel and account exports only include table views

Low

Enterprise admins can disable non-admin exports

Pair-specific challenges

  • CSV-only extraction requires manual UI steps for Ringy

    Ringy has no documented public API, REST endpoint, or developer documentation for programmatic data access. All data extraction relies on the 'Generate CSV' function inside the Ringy UI, which requires a logged-in user session and cannot be automated headlessly. For very large datasets (over 10,000 records), the export may need to be split by date range or filtered subsets manually. We coordinate with the customer to ensure the CSV export is run with 'Include all custom fields' checked and the auto-block keyword filter reviewed before extraction begins.

  • Auto-block keyword filter may silently exclude records from export

    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. Any records found to be silently filtered are flagged for manual review and re-export if recoverable.

  • Drip campaigns and automation sequences have no export path

    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, timing rules, and branching conditions cannot be extracted programmatically. We document the visible campaign structure — names, stages, associated templates, and estimated daily/weekly cadence — as reference metadata for the customer to use when rebuilding sequences in Monday.com's Automation Center. We do not migrate automation logic as code.

  • Call recordings, SMS thread bodies, and attachments cannot be extracted

    Ringy's built-in VOIP softphone stores call recordings and disposition data within its own interface with no documented bulk export path. SMS message bodies and conversation threads are stored within Ringy's messaging interface and similarly lack an export mechanism. File attachments associated with Leads or Companies are not accessible via any documented export path. We preserve any SMS or call data that appears in the Lead CSV activity rows, but full thread history and recording URLs are out of scope. The customer should download any critical call recordings or attachments manually before migration scoping begins.

Migration approach

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

  1. Scoping and export preparation

    We audit the Ringy account structure: record counts for Leads, Contacts, Companies, and Deals; custom field inventory via the 'Include all custom fields' checkbox preview; auto-block keyword list review; and drip campaign structure documentation. We identify any records that may have been silently filtered by auto-block and coordinate with the customer to re-export if needed. The customer runs the CSV export while we scope the Monday.com destination boards, column types, and automation requirements. Discovery output is a written migration scope and field mapping document.

  2. Monday.com destination schema setup

    We configure the Monday.com CRM destination workspace: the People (Contacts) board, Companies board, and Deals board. We create the custom column types to match the Ringy custom fields identified during scoping, set up Status columns matching the Ringy pipeline stages, and configure any List column options from Ringy picklist values. We set up Monday.com Team Members to align with the Ringy Owner structure, resolving by email match. Schema configuration is validated in Monday.com before any data migration begins.

  3. Data extraction and transformation

    We process the Ringy CSV export: deduplicate by email address to prevent duplicate Person records, normalize company data from Lead rows into standalone Company records, split the Lead-to-Contact mapping, transform Ringy custom field values to match Monday.com column types, and map activity rows to Monday.com Activity records linked to the correct Person. We generate a pre-migration reconciliation report showing record counts by object type against the Ringy CSV row counts to confirm nothing was silently filtered.

  4. Pilot migration and reconciliation

    We run a pilot migration of a representative subset (typically 100-500 records per object type) into Monday.com to validate the field mapping, verify column type alignment, confirm activity linking to Person records, and check tag application. The customer reviews the pilot output and identifies any discrepancies. Corrections to the transformation logic are applied before the full production migration. We do not migrate into a Monday.com Sandbox because Monday.com does not offer a per-record Sandbox for CRM boards; the pilot serves as the validation step.

  5. Full production migration

    We run the full migration in record-dependency order: Companies first (since People link to them), then People (Contacts), then Deals (board Items), then Activities. We use Monday.com's API for all destination writes with batch chunking and rate-limit handling. Each phase emits a row-count reconciliation report against the Ringy CSV totals. Any records rejected due to data quality issues (missing required fields, invalid email format) are logged to an exception report for the customer's review and manual correction.

  6. Cutover, delta sync, and automation rebuild handoff

    We freeze Ringy writes during cutover, run a final delta migration of any records modified or added during the migration window, then enable Monday.com as the system of record. We deliver the drip campaign and automation structure inventory document to the customer's admin team for rebuild in Monday.com's Automation Center. We do not rebuild Ringy automations as Monday.com automations inside the migration scope. We support a three-day post-cutover window to resolve any data quality issues surfaced during cutover validation.

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
monday CRM logo

monday CRM

Destination

Strengths

  • Board-based UI makes pipeline stages and deal progress visually obvious without training.
  • No-code automation builder requires no developer resources to create lead routing and stage-triggered actions.
  • Flexible column system supports custom CRM fields without schema changes or admin involvement.
  • Integrates natively with Slack, Gmail, Outlook, and Zapier with minimal configuration overhead.
  • Layered product means teams already on monday Work Management can add CRM without migrating existing data.

Weaknesses

  • No native Contacts object separate from Items — contacts are managed inside a CRM module's People feature.
  • Pipeline and deal relationships use a flat item model rather than a relational object model, making complex CRM associations awkward.
  • Automations are plan-gated (250 actions/month on Standard, 25,000 on Pro) and the legacy Recipe system is being deprecated.
  • Customization and advanced views (Chart, Formula, Dependency) are locked behind Pro and Enterprise tiers.
  • Per-seat pricing with non-refundable annual billing creates cost lock-in risk during migration.

Complexity grading

How hard is this migration?

Moderate CRM migration. 4 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 monday CRM.

  • Object compatibility

    C

    4 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 monday CRM 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 monday CRM data migrations

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

Can't find your answer?

Walk through your Ringy (formerly iSales) to monday CRM 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 three weeks for accounts under 10,000 Leads and 2,000 Deals with standard Ringy export columns and no complex custom field dependencies. Migrations with large custom field sets, multi-pipeline Deal structures requiring separate Monday.com boards, significant data-cleaning requirements (deduplication, format normalization), or a large volume of activity records requiring timeline reconstruction move to five to eight weeks. The primary time variable is the Ringy CSV export preparation and the customer review cycle for the pilot migration.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Ringy (formerly iSales).
Land in monday CRM, 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