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 KeystoneJS. Where KeystoneJS 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 KeystoneJS, review sample records from it and propose how it can be represented, based on what KeystoneJS 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.
We've built custom modules and integrations on Kentico. Can you migrate their content to KeystoneJS?
We migrate the content and data your custom modules hold, as long as it can be read from Kentico programmatically. Every migration we run is written as custom code for that project rather than pushed through an off-the-shelf tool, so unusual module data is not a blocker. During scoping we review each custom module and integration with you and agree how it will be handled before any work is committed.
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 KeystoneJS will send messages about the migrated data: we import with notifications switched off wherever KeystoneJS 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 KeystoneJS can't take in through an API?
In many cases, yes. Where something can't be written through an API, we recreate it through KeystoneJS'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 KeystoneJS requires fields our Kentico 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 KeystoneJS 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 change our URL structure when we move from Kentico to KeystoneJS, such as moving a blog or docs from a subdomain onto our main domain?
Yes, where KeystoneJS and your site's front end support the structure you want. Each page is created in KeystoneJS by the migration, so it can be given its new address, for example a blog moved from a subdomain to a path on your main domain, and you get a map of every old URL to its new one so redirects can be set up from the old addresses wherever they are served.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
