Can Splits move between Workspaces?

Question

Using the Workspace feature to allow developers and teams to create Splits, Segments and Traffic Types in their own workspace, is it possible to migrate existing Splits from one Workspace to another?

Answer

There is no migration path for existing Splits between Workspaces. This is due to the fact that Environments, API Keys, Segments, and Traffic Types are all children of and are unique to a single workspace, so to cut over a split from one workspace to another you’d need to also move or copy any segments used by that split.  You probably want to make sure the traffic type is consistent, though that’s not really required. 

You will need to change the API key used in code for splits that are moved, so you’ll want to leave any splits getting traffic in place, copy the split to the new workspace, change the API key, traffic will start flowing to the new workspace, and then you can delete the split from the original workspace.

Finally, if any of the splits are using random, percentage-based targeting the bucketing will change when the split is recreated in the new workspace.

What we recommend instead, if possible, is to create the workspaces needed for each team and have them start to use those workspaces for all their net new releases. All existing releases should continue forward and be completed in the current "Default" workspace and then removed from the code in the normal fashion.

In this manner there will be no potential impact on existing flags, allowing to incrementally phase teams into their own workspaces.