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 Groove Knowledge Base. Where Groove Knowledge Base 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 Groove Knowledge Base, review sample records from it and propose how it can be represented, based on what Groove 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 eDesk Knowledge Base content or formatting that has no equivalent in Groove Knowledge Base?
We map it to the closest equivalent Groove 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 our eDesk Knowledge Base design and theme carry over to Groove Knowledge Base?
No. The visual theme is set up separately in Groove Knowledge Base, because each platform builds its theme in its own way and themes don't convert from one platform to another. Your articles migrate as normal, so the new theme can be applied on top of them.
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 Groove Knowledge Base will send messages about the migrated data: we import with notifications switched off wherever Groove Knowledge Base 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 Groove 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 Groove Knowledge Base'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 Groove Knowledge Base requires fields our eDesk Knowledge Base 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 Groove 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.
Can you migrate the version history of our eDesk Knowledge Base content to Groove Knowledge Base, and is there a limit on how many versions come across?
It depends on Groove 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 Groove Knowledge Base can hold past versions, any cap on how many it keeps is Groove Knowledge Base's own, so we confirm it with you during scoping.
Will our eDesk Knowledge Base page hierarchy, structure and categories stay the same in Groove Knowledge Base, or do we need to set them up 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 Groove 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 Groove 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 eDesk Knowledge Base folder and page structure during the migration, for example if Groove Knowledge Base allows fewer levels?
Yes. You can set up the structure you want in Groove 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 Groove Knowledge Base's API where it allows that, which is faster than moving pages by hand. Where Groove Knowledge Base allows fewer levels than eDesk Knowledge Base, 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
