Handle-cms-migrations-in-code

Key Takeaways

• Migrations are needed any time a schema change would break existing content—field renames, type changes, structural refactors
• The core pattern is query → transform → write back, ideally wrapped in a transaction
• Always test migrations against a copy of production data before running against live content
• Version and commit migration scripts alongside schema changes so they're reproducible
• Use atomic transactions where your CMS supports them to avoid partial writes