A Concrete CMS replacement should be evaluated with the existing page tree, block types, areas, themes, permissions, workflows, multilingual structure, forms, search, and add-ons. Prototype the most complex page and editor task, then compare versioning, scheduled publishing, accessibility, caching, APIs, and deployment. Inventory custom blocks and package code early because they often drive migration cost. Preserve paths, redirects, metadata, files, and historical versions where required. Plan editor training and a reversible, staged launch.
Akousa