Convert Between Content Types
Why convert content types
Section titled “Why convert content types”Content types evolve as your site matures. A simple “Article” page type might split into “News Article” and “Blog Post” with different layouts and fields. A redesign might consolidate multiple page types into one. Converting existing pages to a new content type is faster and safer than recreating them from scratch because you keep the page identity, URL, version history, and access rights intact.
How conversion works
Section titled “How conversion works”When you convert a page to a different content type, the CMS tries to map properties from the old type to the new type. Properties with the same name and compatible data types transfer automatically. Properties that exist only on the old type or only on the new type require your attention.
| Scenario | What happens |
|---|---|
| Property name and type match | Value transfers automatically |
| Property name matches but type differs | CMS attempts conversion; may lose data if types are incompatible |
| Property exists only on the old type | Value is discarded unless you map it manually |
| Property exists only on the new type | Field is left empty on the converted page |
Convert a single page
Section titled “Convert a single page”- Navigate to the page you want to convert in the content tree.
- Right-click the page and select Convert to Another Type or open Tools > Convert Page Type.
- Select the target content type from the dropdown list.
- Review the property mapping table. The CMS shows which properties transfer automatically and which are unmapped.
- For unmapped properties, choose a target property to map to, or accept that the value will be lost.
- Click Convert or Apply.
- The CMS creates a new version of the page with the new content type. The previous version remains in the version history.
- Verify the converted page by opening it in the editor and checking all fields.
Test conversion before applying
Section titled “Test conversion before applying”Always test conversions on non-critical content first to avoid data loss.
- Create a copy of the page you want to convert.
- Perform the conversion on the copy.
- Open the converted copy and verify:
- All important content transferred correctly.
- No fields show missing or corrupted data.
- The page renders correctly in preview.
- If the test conversion looks correct, proceed with the actual page.
- If you see problems, adjust property mappings or update the target content type before converting the real page.
Bulk conversion
Section titled “Bulk conversion”When you need to convert many pages at once, bulk conversion saves time.
- Open the Admin section.
- Navigate to Content Type management or Tools > Change Content Type.
- Select the source content type (the type you want to convert from).
- Select the target content type (the type you want to convert to).
- The CMS shows a list of all pages using the source content type.
- Review the property mapping for the bulk operation.
- Select all pages or a subset to convert.
- Click Convert.
- Monitor the progress. Large bulk conversions may take several minutes.
- Verify a sample of converted pages to confirm data integrity.
What happens to unmapped properties
Section titled “What happens to unmapped properties”When a property exists on the old content type but has no match on the new type:
- The value is not deleted from history. Previous versions of the page still contain the old property values. If you convert back to the original type, those values may be recoverable.
- The value is not available on the new type. The converted page simply does not have that field, so the value is not displayed or editable.
- Rich text content is usually safe. Rich text fields named the same way on both types transfer without loss.
- Blocks and references may break. If the new type uses a different content area structure, block references may not transfer correctly.
Best practices
Section titled “Best practices”- Map properties explicitly. Do not rely on automatic mapping for critical content. Review every field.
- Test on copies first. Convert a duplicate page and verify before touching the original.
- Plan bulk conversions during low-traffic periods. Large conversions can affect editor performance temporarily.
- Communicate with content authors. Warn editors that converted pages may need manual review, especially for unmapped fields.
- Keep old content types temporarily. Do not delete the old content type until you verify all conversions completed successfully.
1. A developer adds a new 'Blog Post' content type and wants to convert 200 existing 'Article' pages to it. The Article type has a 'Sidebar' content area that does not exist on Blog Post. What happens to the sidebar content?
Unmapped property values are not transferred to the new type but remain in version history. If you convert back to the original type, the values may still be recoverable. They are not permanently deleted.
Unmapped property values are not transferred to the new type but remain in version history. If you convert back to the original type, the values may still be recoverable. They are not permanently deleted.
Review this topic →2. Before converting 50 product pages to a new content type, what is the safest first step?
Testing the conversion on a copy of a single page lets you verify property mappings and identify potential data loss before affecting any real content. This is the safest way to catch problems early.
Testing the conversion on a copy of a single page lets you verify property mappings and identify potential data loss before affecting any real content. This is the safest way to catch problems early.
Review this topic →