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 Podium. Where Podium 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 Podium, review sample records from it and propose how it can be represented, based on what Podium 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 Podium will send messages about the migrated data: we import with notifications switched off wherever Podium 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 Podium can't take in through an API?
In many cases, yes. Where something can't be written through an API, we recreate it through Podium'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 Podium requires fields our Missive 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 Podium 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.
How will we tell migrated records apart from the ones already in Podium?
We can mark every migrated record in Podium, for example with a custom checkbox field such as "Migrated from Missive", 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 Podium.
Do internal notes and system-generated notes from Missive migrate to Podium, or only customer-facing replies?
Internal notes can come across, and so can system-generated notes where Missive's API makes them available. During scoping you choose which notes to include, so Podium holds the history your team will actually use.
Can you combine data from Missive and other support tools into one Podium account?
Yes. Each tool's data is extracted separately and written into the same Podium 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 you migrate every conversation under our Missive labels to Podium, with full threads, not just the ones in my own inbox?
Yes, as long as the Missive user we connect as can see them. Missive's API works through one user's personal token and lists the conversations visible to that user, including shared accounts they can access, and Missive notes that message bodies may be redacted where that user isn't the author or a recipient of a message, or following the conversation, so we confirm during scoping that the user can reach every label and mailbox you need. We can then give you a count of conversations per label so you can confirm everything came across.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
