This guide provides a step-by-step overview of how to consolidate multiple Workpath instances into a unified Workpath account using Business Units (BUs). To learn whether BUs are the right way to structure your organization, see Business Units.
Migration Process Overview
The migration process is broken down into three main phases: Before, During, and After. Each step involves coordination between the Customer and Workpath teams to ensure a smooth transition.
Testing the Migration
Workpath offers to conduct the BU migration in a test environment with a replica of your production data. If you would like to make use of this option, inform your Client Success Manager.
1. Before Migration
Key Steps:
-
Define Scope of Migration:
Workpath and the Customer agree on which Workpath instances will be merged. For example,acme-sub.workpath.comwill be merged intoacme.workpath.comas a new Business Unit. -
Decide on Visibility Settings:
The Customer determines whether the new Business Unit should be:- Private: Goals are visible only to members of the Business Unit.
- Public: Goals are visible across all Business Units by default.
-
Set Up Single Sign-On (SSO):
Configure SSO to enable secure user provisioning and efficient management of membership in Business Units. Follow Workpath's Entra ID SSO integration guide. -
Review Integrations:
Review current integrations, such as Jira or Azure DevOps, during this phase. Some integrations may require manual reconfiguration before or after the migration process. -
Schedule a Migration Time Window:
Collaborate with Workpath to finalize a migration timeframe. Migrations are typically scheduled during the evening hours to minimize impact on users. Migrations generally take 30 minutes or less.
2. During Migration
Migration Process:
-
Enter Maintenance Mode:
Both the source and target accounts are switched into maintenance mode. During this period, users cannot access Workpath, and a message informing about the migration is displayed instead. -
Copy All Data:
Data from the source Workpath account is securely migrated into the target account as part of its new Business Unit:- All data is copied, including Strategic Elements, KPIs, Goals and Key Results, Initiatives but also Teams, Conversations, Goal Filters …
- User deduplication: If a user exists in both the source and target accounts, a single, merged user account is created. This account will belong to both the existing and new BUs.
-
Set Up Redirects:
Workpath creates a permanent redirect from the old instance (e.g.,acme-sub.workpath.com) to the new instance (e.g.,acme.workpath.com). Additionally, a notification is added to the login page to inform users of the change.
3. After Migration
Post-Migration Actions:
-
Reconnect API Tokens:
API tokens from the source account (e.g.,acme-sub.workpath.com) will no longer function after the migration. The Customer needs to recreate new API tokens in the target instance to restore integration functionality.
Why Migrate to Business Units?
Consolidating into Business Units enables more cohesive management of Goals and Teams, while still maintaining segmentation for specific departments or divisions. By partnering with Workpath, your organization ensures a seamless and efficient migration process that maximizes collaboration and alignment moving forward.