Will original ownership, authorship and created dates be preserved when we migrate to October CMS?
Yes. Created-time metadata is carried across, and ownership and authorship are carried across where the original users are set up in October CMS. Where October CMS cannot store one of them natively, it is kept as embedded metadata on the migrated record.
If October CMS 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 October CMS, review sample records from it and propose how it can be represented, based on what October CMS 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 our current CMS. Can you migrate their content to October CMS?
We migrate the content and data your custom modules hold, as long as it can be read from your current CMS 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 migrating to October CMS 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 October CMS will send messages about the migrated data: we import with notifications switched off wherever October CMS 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 October CMS 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 October CMS requires fields our current data doesn't have?
We check October CMS 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 October CMS 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.
What data will be migrated to October CMS, 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 October CMS, including anything that won't move, and you confirm the scope.
What happens if some of our field values are longer than October CMS allows?
We handle it in the migration scripts. Fields where October CMS'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.
Will the migration delete or overwrite any data that's already in October CMS?
No. The migration adds your records alongside what is already in October CMS, 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 October CMS 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 October CMS 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.
Can you change our URL structure as we move to October CMS, such as moving a blog or docs from a subdomain onto our main domain?
Yes, where October CMS, or the front end that serves your site, supports the structure you want. Each page is created in October CMS 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
