Overview

Recent updates to the Contently platform have modified how stories can be cloned across different versions of the story editor (V1, V2, and V3). These changes impact both cross-publication and same-publication cloning behavior. While forward cloning from older to newer editors is generally supported, backward cloning from newer to older versions is restricted due to architectural differences in the editors' underlying content models. This article outlines the current capabilities, limitations, and available alternatives when cloning stories between editors.

Solution

Supported Cloning Scenarios

The following matrix outlines the supported cloning behavior based on the source and target editor versions:

Same Publication Cloning

Note: Once a publication is configured to use the V3 editor, cloning stories to older versions within the same publication is not allowed due to current platform design limitations.

Cross-Publication Cloning

All editor version combinations are supported for cross-publication cloning.

Alternative Options When Cloning is Not Supported

In cases where cloning is restricted, such as V3 to V1/V2 within the same publication, manual migration is available.

Migration Support

Contently engineering can perform a manual migration that:

• Retains the original story content.

• Adds “Clone” to the title of the duplicated story for clear identification.

How to Request a Migration

1. Collect the URLs of the stories that need to be cloned.

2. Note the error message received during the cloning attempt.

3. Submit a support ticket with the following details:

   • The list of story URLs.

   • The specific error message.

   • A request for migration to complete the cloning process.