Will the original assignees, message authors and created dates be preserved?
Yes. Created-time metadata is carried across, and so are assignees and message authors who have a user account in Missive. Where Missive cannot store one of them natively, it is kept as embedded metadata on the migrated record.
If the new system 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 Missive, review sample records from it and propose how it can be represented, based on what Missive 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 the migration set off automations or 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 Missive will send messages about the migrated data: we import with notifications switched off wherever Missive allows it, and either pause any automation that could send them for the migration window or give it a condition, such as a suppression tag, that skips migrated records, which lets your live automations keep running for new 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 Missive can't take in through an API?
In many cases, yes. Where something can't be written through an API, we recreate it through Missive's user interface 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 Missive requires fields our Enchant data doesn't have?
We check the destination for required fields your source 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 Missive 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.
Do internal notes and system-generated notes from Enchant migrate to Missive, or only customer-facing replies?
Internal notes can come across, and so can system-generated notes where Enchant's API makes them available. During scoping you choose which notes to include, so Missive holds the history your team will actually use.
Can you combine data from Enchant and other support tools into one Missive account?
Yes. Each tool's data is extracted separately and written into the same Missive account. How records from the different tools fit together is settled in the data mapping before the build. The sample migration includes data from every source, so you can check the combined result before the full run.
Can our Enchant internal notes be migrated into Missive?
Yes, for conversations whose emails are in a mailbox connected to Missive. Each note is attached to its matching conversation, which we find by the email's Message-ID, so any mailbox reconnections should be finished before the notes are migrated, since Missive rebuilds a mailbox's threads when it is reconnected. Notes may show the date they were migrated rather than their original date, so you check how they appear in the sample migration before the full run.
What can you migrate from Enchant into Missive, such as email history, attachments and custom fields?
We migrate your contacts and labels into Missive, and internal notes where Missive's API allows it, while your email history and its attachments come in through the mailboxes you connect. Missive pulls in the email already in each connected mailbox itself, as far back as your Missive plan and email provider allow, so the migration adds what Missive can't fetch on its own, such as labels and notes, onto the matching conversations. Custom field values come across where Missive has a place for them. Anything Missive's API can't take, such as rules, is listed in the migration checklist so you know how each item will be handled.
Can you organize our labels in Missive into a parent/child hierarchy without losing data?
Yes. We can restructure your labels in Missive into a parent/child hierarchy without losing any data, and give you a count of the conversations under each label so you can check the result. If some labels belong to specific teams rather than the whole organization, we confirm with you first whether to keep them at team level, which means creating those teams first, or to move them all to the organization level.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
