Will original ownership, authorship and created dates be preserved when we migrate to eDesk Knowledge Base?
Yes. Created-time metadata is carried across, and ownership and authorship are carried across where the original users are set up in eDesk Knowledge Base. Where eDesk Knowledge Base cannot store one of them natively, it is kept as embedded metadata on the migrated record.
If eDesk Knowledge Base 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 eDesk Knowledge Base, review sample records from it and propose how it can be represented, based on what eDesk Knowledge Base 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 eDesk Knowledge Base?
We map it to the closest equivalent eDesk Knowledge Base 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 eDesk Knowledge Base 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 eDesk Knowledge Base will send messages about the migrated data: we import with notifications switched off wherever eDesk Knowledge Base 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 eDesk Knowledge Base 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 eDesk Knowledge Base requires fields our current data doesn't have?
We check eDesk Knowledge Base 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 eDesk Knowledge Base 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.
Will links between our records still work after we migrate to eDesk Knowledge Base?
Yes. We move your data in two passes. The first pass creates every record in eDesk Knowledge Base 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 eDesk Knowledge Base, 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 eDesk Knowledge Base, including anything that won't move, and you confirm the scope.
What happens if some of our field values are longer than eDesk Knowledge Base allows?
We handle it in the migration scripts. Fields where eDesk Knowledge Base'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.
Do you migrate our users, or do we need to create them in eDesk Knowledge Base before the migration?
Usually your team creates them, but we can do it for you. We recommend setting up your users in eDesk Knowledge Base 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 eDesk Knowledge Base allows it.
Will the migration delete or overwrite any data that's already in eDesk Knowledge Base?
No. The migration adds your records alongside what is already in eDesk Knowledge Base, 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 eDesk Knowledge Base 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 eDesk Knowledge Base 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 eDesk Knowledge Base's plan limits or storage charges?
It depends on your eDesk Knowledge Base plan. Migrated records arrive as regular records in eDesk Knowledge Base, so whether they count toward its record or storage limits is set by eDesk Knowledge Base'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.
Can you migrate the version history of our files and documents to eDesk Knowledge Base, and is there a limit on how many versions come across?
It depends on eDesk Knowledge Base: 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 eDesk Knowledge Base can hold past versions, any cap on how many it keeps is eDesk Knowledge Base's own, so we confirm it with you during scoping.
Will our page hierarchy, structure and categories stay the same when we migrate to eDesk Knowledge Base, 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 eDesk Knowledge Base 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 eDesk Knowledge Base 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.
Can you reorganize our folder and page structure as we migrate to eDesk Knowledge Base, for example if eDesk Knowledge Base allows fewer levels?
Yes. You can set up the structure you want in eDesk Knowledge Base first, and we write the migration scripts to place each page into it. Or we migrate everything as it is and restructure it afterwards through eDesk Knowledge Base's API where it allows that, which is faster than moving pages by hand. Where eDesk Knowledge Base allows fewer levels than your current platform, we agree with you how each level maps before anything runs, and the sample migration shows the result.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
