Your digital humanities site is a decade old. It was cutting-edge when it launched, custom-built to showcase a unique collection with features no off-the-shelf platform could provide. Now the security warnings are piling up, the original developers are long gone, and staying on a supported version of Rails becomes its own project. "Migration" is the wrong word for what you need. Migration assumes your data is portable. If your site predates broad IIIF adoption (roughly 2015-2