A practical guide to safely modifying Prismic content models on live sites without losing published content. Covers four common scenarios: renaming a field (change label, keep ID), changing a field's type (add new field, migrate content via Migration API, switch code, remove old field), splitting one field into two, and making a single field repeatable. Each technique follows the same pattern: add new fields alongside old ones, use the Prismic Migration API with a Node.js script to move content, update application code, then remove the old field. Also covers redesigning slice variations by adding a new variation and gradually migrating content writers to it.
Table of contents
Working with an AI agent? Point it here.Tools we'll be usingChange a field's nameChange a field's typeBest done with AISplit a field into twoMake a single field repeatableChange the design of a sliceWrap-up1.5K Impressions