Will original ownership, authorship and created dates be preserved?
Yes. Created-time metadata is carried across, and ownership and authorship are carried across where the original users are set up in SharePoint. Where SharePoint 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 SharePoint, review sample records from it and propose how it can be represented, based on what SharePoint 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.
How is rich content, such as embedded video, hyperlinks and web parts, handled during migration?
Rich content and embedded media are validated during the sample migration, before the full migration runs. Pick your most complex piece of content for the sample, so the content types it contains are tested first.
What happens to Slack Canvas content or formatting that has no equivalent in SharePoint?
We map it to the closest equivalent SharePoint offers and agree that mapping with you before the migration runs. The sample migration then shows you the result on your own content, so you can see how anything without a direct match comes across before the full run.
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 SharePoint will send messages about the migrated data: we import with notifications switched off wherever SharePoint 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 SharePoint can't take in through an API?
In many cases, yes. Where something can't be written through an API, we recreate it through SharePoint'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 SharePoint requires fields our Slack Canvas 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 SharePoint 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 SharePoint?
We can mark every migrated record in SharePoint, for example with a custom checkbox field such as "Migrated from Slack Canvas", 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 SharePoint.
Will our Slack Canvas articles and documents keep any comments, inline images and attachments in SharePoint?
Usually, yes. Images, including the inline images in your articles, and attachments are downloaded from Slack Canvas and uploaded into SharePoint, and the image links inside each article are rewritten to point to the new location, so they no longer depend on your old account. Comments can be migrated too where both platforms support them, but some platforms show the migration account as their author, or can't keep the highlight that ties a comment to its passage, so we can add the original commenter and date to each comment. How cleanly comments and embedded images come across depends on the source, so we check it on a sample of your own documents before the full run.
Can you migrate the version history of our Slack Canvas content to SharePoint, and is there a limit on how many versions come across?
It depends on SharePoint: some platforms can't take version history at all. Where a platform can't take it, each document arrives as its latest version, with an authorship and "migrated from" line added. Where SharePoint can hold past versions, any cap on how many it keeps is SharePoint's own, so we confirm it with you during scoping.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
