Will original ownership, authorship and created dates be preserved when we migrate to Rings AI?
Yes. Created-time metadata is carried across, and ownership and authorship are carried across where the original users are set up in Rings AI. Where Rings AI cannot store one of them natively, it is kept as embedded metadata on the migrated record.
If Rings AI can't natively support an old record type, what are my options?
We handle it case by case. While mapping your data, we identify every record type without a direct counterpart in Rings AI, review sample records from it and propose how it can be represented, based on what Rings AI supports: map it to the closest native object, create a custom field or object, fold it into the parent record as text or a note, attach it as a file, or keep it in a read-only archive. You choose the approach, we write the migration scripts to place the data there, so it comes across in the form you choose instead of being left behind, and you see how it looks in a sample migration before we run the full set.
Will migrating to Rings AI send emails or notifications to customers, our team or anyone else?
No. Before the sample or full migration starts, we confirm with you that nothing in Rings AI will send messages about the migrated data: we import with notifications switched off wherever Rings AI allows it, and pause any automation that could send them or give it a condition that skips migrated records. We only proceed once you have confirmed it. If you want anyone told about the move, that message is sent separately, once the migrated data has been checked.
Can you migrate data that Rings AI can't take in through an API?
In many cases, yes. Where something can't be written through an API, we recreate it through the application itself where the interface allows it, and where that work is repetitive we script and automate it. We tell you up front which items are handled this way, because recreating them through the interface can add time to the schedule.
What happens if Rings AI requires fields our current data doesn't have?
We check Rings AI for required fields your current data cannot fill and bring each one to you before those records are migrated. Together we agree how each one is handled, such as a mapping from an existing field, a default value, or, where Rings AI lets that field be made optional, setting it to not required for the migration so you can make it required again once the migration is complete. The migration then runs with that rule applied, so no records are rejected or left behind.
Can I choose how my pipeline stages and statuses map into Rings AI?
Yes. You tell us where each stage, status and field should land in Rings AI, including moving records into a different pipeline or stage name than the one they have today. We build that mapping into the migration scripts, show it to you in a sample migration, and adjust it before the full run if anything needs to change.
Will my custom fields come across to Rings AI, and can I rename them afterwards?
Yes. We agree with you beforehand where each custom field lands in Rings AI and what it is called. We map fields by their internal ID rather than their label, so renaming them in Rings AI after the migration doesn't affect your migrated data.
How will we tell migrated records apart from the ones already in Rings AI?
We can mark every migrated record in Rings AI, for example with a custom checkbox field that names the system it came from, so your team can tell migrated data apart from records created there. We agree the marker with you during scoping so it fits how your team uses Rings AI.
Will links between our records still work after we migrate to Rings AI?
Yes. We move your data in two passes. The first pass creates every record in Rings AI and stores its new ID. The second pass goes back and points each reference at the new record, so links between records lead to the right place.
How will our records carry over if Rings AI organizes leads, contacts and accounts differently from our current CRM?
We map your records to the way Rings AI structures them, so each type of record lands where Rings AI expects it instead of being copied field for field. Before we build anything, we send you a migration checklist showing what moves and where each item lands, for you to review. Most data moves through the platforms' APIs; where an API cannot write something, we fall back to CSV import or manual entry.
What data will be migrated to Rings AI, and how will each type of record map?
It depends on your current platform and the scope you choose, but it is usually the core records and everything attached to them. Before anything runs, we send you a migration checklist showing where each type of record lands in Rings AI, including anything that won't move, and you confirm the scope.
Do we need to create our custom fields in Rings AI before the migration, or do you create them?
Usually we create them as part of the migration. Where Rings AI has no API for creating fields, we set them up through its interface, using admin access you grant us. On some platforms we ask your team to create certain fields and tell us which source field maps to each one, and we confirm which applies to Rings AI during scoping.
Can you migrate our data into Rings AI if another team already uses it, and merge it with the records already there?
Yes. Before creating anything, we check each incoming record, such as a company or contact, against the records already in Rings AI, using a matching rule we agree with you, such as an email address or an ID. Where a match is found, the migrated data is attached to the existing record. Records with no match are either created as new records or set aside on a list for your team to review, whichever you prefer, and if you already keep a mapping between the two systems' names or IDs, we can apply it in the migration scripts. We also map your data into the fields the other team already uses rather than adding duplicate fields alongside them.
Can you set the same value on a field for every record you migrate to Rings AI, such as labelling every contact's phone as 'Mobile'?
Yes, as long as Rings AI lets that field be set through its API. Each migration is a custom script, so we can apply a fixed value to a field on every migrated record. We first test that Rings AI accepts the value, confirm with you, and then apply it across the board, including on records that have already been migrated.
What happens if some of our field values are longer than Rings AI allows?
We handle it in the migration scripts. Fields where Rings AI's limit is shorter than your data are identified while we map your data, the handling for each one is agreed with you before the migration runs, and you can check the result in the sample migration before the full run.
Do you migrate our users, or do we need to create them in Rings AI before the migration?
Usually your team creates them, but we can do it for you. We recommend setting up your users in Rings AI before the full migration, so every record can be attributed and assigned to the right person; the sample migration uses a default user, so it doesn't need them. If you'd rather we create the accounts, send us the list of users and their roles and we provision them for you, where Rings AI allows it.
Will the migration delete or overwrite any data that's already in Rings AI?
No. The migration adds your records alongside what is already in Rings AI, and nothing there is deleted without your confirmation. Where an incoming record matches an existing one, we link to the existing record rather than creating a second copy, and corrections to migrated records are made as updates wherever possible rather than by deleting and recreating them.
What happens if Rings AI rejects some of our records during the migration?
We log each rejected record, fix the cause and push it again. Common causes, such as a required field your data doesn't fill or a value in a format Rings AI doesn't accept, are agreed with you and handled in the migration scripts, and the scripts can be re-run safely without creating duplicates. When the migration finishes, you get a list of every migrated record and of anything left out, with the reason.
Will the data we migrate count toward Rings AI's plan limits or storage charges?
It depends on your Rings AI plan. Migrated records arrive as regular records in Rings AI, so whether they count toward its record or storage limits is set by Rings AI's pricing, and its own team or your implementation partner can confirm how your plan treats them. If limits are a concern, you can reduce what moves, for example by migrating only the last one or two years of history.
Can you migrate the email history on our mail server, such as Microsoft Exchange, into Rings AI along with our CRM records?
Yes, on a best-effort basis where your current CRM has no clean way to export it. For team members who are still with you, Rings AI may be able to sync their mail itself once each person's email account is connected; for people who have left, we bring their messages in as notes on the right records where Rings AI supports notes, retrieving them from your current CRM or your Exchange server, so the history stays intact and attributable.
What happens to contacts that share an email address or telephone number if Rings AI doesn't allow duplicates?
You decide whether they merge or stay separate. A CRM that checks for duplicates through its API returns the existing contact instead of creating a new one, so records sharing an email address or telephone number would otherwise collapse into one contact; we tell you how many records are affected and let you choose. If you want a separate contact for each source record and Rings AI has a setting that allows duplicate contacts, your team switches it on while we migrate them, and we tell you when it is safe to switch it off again.
Can you migrate the history of our deals' stage changes into Rings AI, not just their current stage?
Yes, where your current CRM records stage changes and Rings AI can hold them. Deal-stage history is scoped like any other data: we check what your current CRM keeps for each deal's stage transitions, agree with you how that history is represented in Rings AI's data model, and you review it in the sample migration before the full run.
Can you migrate our products and customers' purchase history into Rings AI, not just contacts?
Yes, where your current CRM's API makes them available. Products and purchase records are scoped like any other data: the migration checklist covers products alongside contacts, notes and tags, and we confirm what each platform's API can read and write before anything runs. Where Rings AI has no native home for purchase history, we agree another form with you, such as a custom field or a note on the contact.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
