Problem: The client has migrated their content from the Classic Translation Editor to the Advanced Translation Editor (ATE) in a test environment and is considering cleaning up the database after the migration, despite the content being mostly individually edited. Solution: We recommend continuing to use one editor, the Advanced Translation Editor, for all site content to maintain consistency and ease of use for translators. After switching from the Classic Translation Editor to the Advanced Translation Editor, existing translations will still be visible on the frontend. However, these translations might be completely or partially missing when opening the post in the Advanced Translation Editor. For more details, you can visit Switching from Classic to Advanced Translation Editor. Additionally, there is no need for a database cleanup after moving to the new editor, even if the content was initially translated using the Classic Editor.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if needed.
