Will original ownership, authorship and created dates be preserved when we migrate to Slack Canvas?
Yes. Created-time metadata is carried across, and ownership and authorship are carried across where the original users are set up in Slack Canvas. Where Slack Canvas cannot store one of them natively, it is kept as embedded metadata on the migrated record.
If Slack Canvas 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 Slack Canvas, review sample records from it and propose how it can be represented, based on what Slack Canvas 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.
What happens to content or formatting that has no equivalent in Slack Canvas?
We map it to the closest equivalent Slack Canvas 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 migrating to Slack Canvas 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 Slack Canvas will send messages about the migrated data: we import with notifications switched off wherever Slack Canvas 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 Slack Canvas 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.
Will links between our records still work after we migrate to Slack Canvas?
Yes. We move your data in two passes. The first pass creates every record in Slack Canvas 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 Slack Canvas, 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 Slack Canvas, including anything that won't move, and you confirm the scope.
Are attachments migrated to Slack Canvas, and how do you make sure none are missed?
Yes. Attachments are downloaded from your current platform and uploaded to Slack Canvas as real files on the same records, wherever Slack Canvas accepts files on that type of record and within its file size limit, not left as links back to the old system. To make sure none are missed, your Migration Validation Report checks attachment integrity by checksum alongside the record-count comparison, and we can also run an attachment count check against your source and share the results. You can review attachments in the sample migration before the full run.
Do you migrate our users, or do we need to create them in Slack Canvas before the migration?
Usually your team creates them, but we can do it for you. We recommend setting up your users in Slack Canvas 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 Slack Canvas allows it.
Will the migration delete or overwrite any data that's already in Slack Canvas?
No. The migration adds your records alongside what is already in Slack Canvas, 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 Slack Canvas 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 Slack Canvas 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 Slack Canvas's plan limits or storage charges?
It depends on your Slack Canvas plan. Migrated records arrive as regular records in Slack Canvas, so whether they count toward its record or storage limits is set by Slack Canvas'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.
Will our documents keep their comments and images when we migrate to Slack Canvas, and are inline images re-hosted?
Usually, yes. Images, including inline images, and attachments are downloaded from your current platform and uploaded to Slack Canvas, and the image links inside each document or article are rewritten to point to the new location, so your content no longer depends on your old account. Comments can be migrated too where Slack Canvas supports 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 files and documents to Slack Canvas, and is there a limit on how many versions come across?
It depends on Slack Canvas: 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 Slack Canvas can hold past versions, any cap on how many it keeps is Slack Canvas's own, so we confirm it with you during scoping.
Will our page hierarchy, structure and categories stay the same when we migrate to Slack Canvas, or do we need to set them up there first?
By default they carry over wherever the new platform supports them, and you don't need to set them up beforehand. We recreate your page tree or categories in Slack Canvas as part of the migration, wherever it supports them, so each page keeps its place under the same parent, and once every page exists, a second pass points internal links at the new pages. Where Slack Canvas organises content differently, we agree the mapping with you first, and any categories you'd rather leave behind are agreed during scoping. You review the structure in the sample migration before the full run.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
