Migrate our monolithic site to a headless CMS
Employer
Dmytro
Project parameters
Type of cooperationOne-time project
SectionWeb development
Prepaymentwithout prepayment
Payment methodsCash, Bank transfer
Acceptance of requestsfrom today, 04:25 until Sep 14, 2026
Project description
We run an ageing monolithic website where the content, templates and business logic are tangled together in one codebase. Every editorial change turns into a developer ticket, page loads are slow, and adding a mobile app or a second landing site is nearly impossible because there is no clean content API. We want to move to a headless architecture: a modern headless CMS (we are considering Strapi, Contentful or Sanity) as the content backend, and a separate, fast decoupled front-end that consumes content over an API. The goal is a stack that editors actually enjoy and that loads in well under two seconds.
The core of the job is content modeling done properly. We need you to audit our existing pages, define reusable content types, components and relations, and then migrate the real data into the new CMS with a scripted, repeatable import rather than manual copy-paste. Editor workflows matter to us: drafts, preview, scheduled publishing, roles and permissions, and localization support should all work on day one. The new front-end should be statically generated or server-rendered for speed, with clean caching and image optimization.
Preserving search rankings is non-negotiable. Every old URL must resolve, so we need a full redirect map (301s), correct canonical tags, sitemaps, structured data and parity in meta content. Please plan the cutover so there is no downtime and a clear rollback path. We can provide database access, brand assets and a staging environment.
— Content model, migration scripts and data import
— Decoupled front-end with fast rendering and caching
— Editor workflows: drafts, preview, scheduling, roles
— Redirects, canonicals, sitemaps and SEO parity
The core of the job is content modeling done properly. We need you to audit our existing pages, define reusable content types, components and relations, and then migrate the real data into the new CMS with a scripted, repeatable import rather than manual copy-paste. Editor workflows matter to us: drafts, preview, scheduled publishing, roles and permissions, and localization support should all work on day one. The new front-end should be statically generated or server-rendered for speed, with clean caching and image optimization.
Preserving search rankings is non-negotiable. Every old URL must resolve, so we need a full redirect map (301s), correct canonical tags, sitemaps, structured data and parity in meta content. Please plan the cutover so there is no downtime and a clear rollback path. We can provide database access, brand assets and a staging environment.
— Content model, migration scripts and data import
— Decoupled front-end with fast rendering and caching
— Editor workflows: drafts, preview, scheduling, roles
— Redirects, canonicals, sitemaps and SEO parity
