Case studiesHealth information and community

Breastcancer.org: content migration and shared sign-in

Breastcancer.org needed reusable content and a connected sign-in experience. Paulo Cardoso worked on the move from WordPress to Contentful and on single sign-on across the community forum and medical platform.

Business
Breastcancer.org
Sector
Health information and community
Scope
Content migration and shared sign-in
Contributor
Paulo Cardoso
Editorial illustration: open reference books connected by an orange bookmark
AI-generated editorial illustration of the project’s domain.

Content and identity lived in separate systems.

The organization’s content delivery was tied to WordPress. New products needed a way to use the same structured content without inheriting a page-oriented application as their foundation.

The community forum and medical platform also had separate logins. Connecting those experiences required work on identity as well as publishing. Existing URLs were an important migration requirement because people already used them to reach the organization’s information.

Move content to an API and connect the sign-in experience.

Paulo worked on migrating content from WordPress to Contentful. The headless CMS exposed structured content through a GraphQL API, giving new interfaces a shared source to build against.

Single sign-on connected the community and medical experiences. The migration work included preserving existing URLs, treating access to published information as part of the cutover rather than a cleanup task afterward.

What the workflow includes

  • Move publishing content from WordPress to Contentful.
  • Expose structured content through GraphQL.
  • Connect sign-in across the forum and medical platform.
  • Carry existing URL paths into the migration plan.

Project details

Diagram showing Breastcancer.org moving content from WordPress to Contentful and using single sign-on across the forum and medical platform

Project materials showing the workflows and interfaces described in this case.

Reusable content and one identity across the products.

Content became available to multiple products through an API, and people could use a shared identity across the connected experiences. The work changed the underlying content and identity systems while retaining the familiar routes into the organization’s information.

What this means for the technology owner.

A content migration is also a continuity project. The system map should cover publishing, identity, redirects and every product consuming the content API. A replacement team needs those relationships documented to change the platform without breaking how people reach or use the information.

How to hand over software to a new team →

ContentfulGraphQLWordPress migrationSingle sign-onSEO continuity

Project contribution: Paulo Cardoso. The scope described above identifies the work behind this case.

Editorial review: Ego Eimi · Updated September 6, 2026 · About the team

Related case studies

Editorial illustration: dance sneakers and a rehearsal step with one orange lace
Dance education

FitDance

Platform migration and payments

Read the case →
Editorial illustration: architectural house models joined by one orange threshold
Residential real estate

Mark Spain Real Estate

Backend, content and partner integrations

Read the case →
All case studies46 projects

Your technology

Start with the business

Your business depends on it.

Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.

Start a conversation More case studies