Will original ownership, authorship and created dates be preserved when we migrate to Charlie?
Yes. Created-time metadata is carried across, and ownership and authorship are carried across where the original users are set up in Charlie. Where Charlie cannot store one of them natively, it is kept as embedded metadata on the migrated record.
If Charlie 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 Charlie, review sample records from it and propose how it can be represented, based on what Charlie 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 Charlie 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 Charlie will send messages about the migrated data: we import with notifications switched off wherever Charlie 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 Charlie 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 Charlie requires fields our current data doesn't have?
We check Charlie 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 Charlie 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.
We use a lot of custom fields. Can you map them to Charlie?
Where Charlie has a place for them, yes. Each migration is a custom script written for your project, so your custom fields and structure are mapped to Charlie's model rather than forced through an import template. Where field types differ, such as a value stored as text in your current system that Charlie needs as a number, the script converts it. We agree the mapping with you and prove it on a sample migration before the full run.
Will links between our records still work after we migrate to Charlie?
Yes. We move your data in two passes. The first pass creates every record in Charlie 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.
What data will be migrated to Charlie, 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 Charlie, including anything that won't move, and you confirm the scope.
What happens if some of our field values are longer than Charlie allows?
We handle it in the migration scripts. Fields where Charlie'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.
Will the migration delete or overwrite any data that's already in Charlie?
No. The migration adds your records alongside what is already in Charlie, 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 Charlie 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 Charlie 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 Charlie's plan limits or storage charges?
It depends on your Charlie plan. Migrated records arrive as regular records in Charlie, so whether they count toward its record or storage limits is set by Charlie'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.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
