For a Cockpit CMS migration, inventory collections, singletons, fields, locales, assets, users, permissions, webhooks, and every application consuming its API. Compare alternatives using the most complex content model and production-like queries. Validate authentication, filters, pagination, media URLs, caching, drafts, revisions, and extension points. Self-hosting requirements, database support, backups, upgrades, and security response should be explicit. Build a compatibility layer or coordinated rollout so frontends do not break during data migration.
Akousa