The legacy branching feature is being retired, and all existing legacy branches will be either migrated to the current experience or permanently deleted.
The deprecation exclusively affects customer projects that contain active legacy branches. Projects without any legacy branches are not impacted, and no action is necessary.
Legacy branches are identifiable by a visual tag (v1) in both the branches table and the Strings editor.
Deprecation timeline
June 1, 2026:
-
Empty legacy branches that have not been updated in the past 90 days will be permanently deleted.
-
The majority of active legacy branches will undergo an automatic migration to the new format.
After June 1, 2026:
-
For a small number of branches that cannot be migrated automatically, the assigned Customer Success representative will contact customers directly to coordinate a guided migration.
Migration paths
There are two distinct paths for transitioning branches from legacy to new branching, determined by the technical characteristics of the branch.
Automatic migration
Most legacy branches are eligible for automatic migration. This is a backend process that converts the branch to new branching while preserving all data, branch IDs, and existing integrations. This path requires no customer action and causes no disruption to workflows.
Guided migration
A small subset of branches requires a guided migration process led by a Customer Success representative. This path is necessary for branches with technical complexities that prevent automatic conversion.
If a branch requires guided migration, certain data cannot be transferred. Review the implications below carefully before the migration date:
-
New Branch ID: The migrated branch will receive a new, unique ID. All API references, CLI configurations, and other integrations pointing to the old branch ID will need to be updated manually.
-
Data Attribution: All migrated data will be attributed to the user account that originally created the branch, regardless of which user performed the work.
-
Important
Data Not Migrated: The following items will not be present in the migrated new branch:
-
Screenshots created within the branch.
-
Comments created within the branch.
-
Specific metadata, such as format annotations or pre-translation flags.
-
Changes made to excluded translations.
-
If a branch is affected, Phrase will share detailed information about the implications and coordinate a migration date. Phrase will manage the technical aspects of the migration, and no action will be required from the user.