CRM migration
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)
Source
monday CRM
Destination
Compatibility
6 of 8
objects map 1:1 between Ringy (formerly iSales) and monday CRM.
Complexity
CModerate
Timeline
2-3 weeks
Overview
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.
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 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
monday CRM
Person (Contact)
1:1Ringy 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
monday CRM
Person (Contact)
1:1Ringy 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
monday CRM
Company
1:1Company 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
monday CRM
Deal (board Item)
1:1Ringy 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
monday CRM
Status Column
lossyRingy 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
monday CRM
Activity (Emails & Activities)
1:1Activity 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
monday CRM
Custom Columns
lossyRingy 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
monday CRM
Tag
1:1Tags 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.
| Ringy (formerly iSales) | monday CRM | Compatibility | |
|---|---|---|---|
| Lead | Person (Contact)1:1 | Fully supported | |
| Contact | Person (Contact)1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Deal (board Item)1:1 | Fully supported | |
| Deal Stage | Status Columnlossy | Fully supported | |
| Activity | Activity (Emails & Activities)1:1 | Fully supported | |
| Custom Properties | Custom Columnslossy | Mapping required | |
| Tag | Tag1: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
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Ringy (formerly iSales)
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 4 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 monday CRM.
Object compatibility
4 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 monday CRM migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Ringy (formerly iSales)
Other ways to arrive at monday CRM
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.