Skip to content
Optimizely CertificationOptimizely Certification Optimizely Certification

Publish from CMP to CMS

⏱ 15 minutes intermediate
📜CoreCMPcms

Why publish from CMP instead of directly in CMS

Section titled “Why publish from CMP instead of directly in CMS”

When content authors work directly in CMS, they bypass the editorial workflow — there is no structured review process, no campaign context, and no visibility into what other content is being produced at the same time. This works for quick edits, but it breaks down when teams produce content at scale.

Publishing from CMP means content goes through a defined approval pipeline before it ever reaches CMS. By the time content arrives in CMS, it has been reviewed, approved, and is ready to go live. This separation keeps CMS focused on delivery while CMP handles production.

What you will do

Section titled “What you will do”
  1. Complete content in CMP and move it through approval
  2. Map CMP content fields to CMS content type fields
  3. Push approved content to CMS
  4. Review the content in CMS and schedule or publish

Complete content and get approval

Section titled “Complete content and get approval”

Before content can be published to CMS, it must reach the final stage of your CMP workflow. The exact stages depend on how your team has configured workflows, but a typical path looks like this:

  1. Draft — Author writes content in CMP’s editor
  2. Editorial review — An editor checks writing quality, tone, and accuracy
  3. Brand review — A brand manager verifies messaging alignment and visual guidelines
  4. Final approval — A stakeholder or content lead signs off

At each stage, reviewers can:

  • Approve — Move content to the next stage
  • Request changes — Send content back to the author with comments
  • Reject — Stop the content from progressing (with a required explanation)

When content reaches the final approval stage and is approved, it becomes eligible for CMS publishing.

Understand field mapping

Section titled “Understand field mapping”

CMP content and CMS content types have different structures. Field mapping defines how CMP fields translate to CMS properties when content is pushed.

CMP fieldCMS propertyNotes
TitlePage name / Title propertyTypically a one-to-one mapping
BodyMain body / XhtmlStringRich text transfers with formatting intact
SummaryTeaser text / Short descriptionUsed for SEO and content previews
Featured imageHero image / Content referenceImage assets transfer to CMS media library
TagsCategories or tagsDepends on CMS taxonomy configuration
Publish dateScheduled publish dateControls when the page goes live

Your CMP admin configures field mappings for each content type pair. If a mapping does not exist for the content type you are publishing, contact your admin to set one up before proceeding.

Push content to CMS

Section titled “Push content to CMS”

Once content is approved and field mappings are configured:

  1. Open the approved content item in CMP
  2. Select Publish to CMS from the actions menu
  3. Choose the target CMS content type and destination (which page tree location the new page should appear under)
  4. Review the field mapping preview — CMP shows you which CMP fields map to which CMS properties
  5. Resolve any mapping warnings (e.g., a required CMS field with no CMP equivalent)
  6. Select Push to CMS

CMP creates a draft page in CMS with all mapped fields populated. Images and other assets are uploaded to the CMS media library automatically.

What happens if content already exists in CMS

Section titled “What happens if content already exists in CMS”

If you are updating content that was previously published from CMP:

  • CMP detects the existing CMS page and updates it rather than creating a duplicate
  • A new version is created in CMS, preserving the version history
  • The updated content starts as a draft in CMS, even if the previous version was published

Review and publish in CMS

Section titled “Review and publish in CMS”

After pushing from CMP, open CMS to review the content:

  1. Navigate to the page in the CMS content tree (CMP provides a direct link after pushing)
  2. Verify the content renders correctly in the CMS preview
  3. Check that images, links, and formatting transferred properly
  4. Fill in any CMS-specific fields that do not have CMP equivalents (e.g., navigation settings, SEO metadata not covered by CMP)
  5. Publish immediately or schedule the page for a future date

Handle publishing errors

Section titled “Handle publishing errors”

Common issues and how to resolve them:

IssueCauseResolution
Missing required fieldsCMS content type has required properties without CMP mappingFill in the missing fields manually in CMS, or ask your admin to add the mapping
Image upload failureImage exceeds CMS file size limits or uses an unsupported formatResize or convert the image in CMP before re-pushing
Duplicate page createdField mapping lost the connection to the existing pageDelete the duplicate in CMS and re-push from CMP, selecting the correct target page
Formatting differencesRich text rendering differs between CMP and CMS editorsAdjust formatting in CMS after push — minor differences in spacing or heading styles are normal

Best practices

Section titled “Best practices”
  • Do not edit pushed content in both systems — Choose one system of record. If CMP is the authoring tool, make edits in CMP and re-push. Editing in both places creates version conflicts.
  • Test field mappings with a sample item — Before pushing an entire campaign’s worth of content, push one item and verify everything maps correctly.
  • Coordinate publish timing — If your campaign has a specific launch date, push content to CMS in advance and use CMS scheduled publishing to coordinate the go-live moment.
  • Keep CMP status updated — After publishing in CMS, update the CMP content item’s status to “Published” so the campaign dashboard reflects the true state.