Follow this guide in order to migrate your Users, Teams, Goals and Projects from Microsoft Viva Goals to Workpath.
Step 1: Set up Authentication
Workpath prioritizes security and ease of use, offering multiple ways to set up single sign-on and automatic provisioning integrated with your Azure Entra ID directory.
To ensure the most seamless experience, we recommend:
- Configuring single sign-on via SAML for secure and seamless authentication
- Configuring automatic provisioning via SCIM in order to fully manage your Workpath users and licenses inside Azure Entra ID
Step 2: Import data from Viva Goals
Workpath is capable of importing this data from Viva Goals:
- Users
- Teams, including their hierarchy
- Goals
- Key Results
- Initiatives
- Check-ins (as status updates or notes)
- Tags (as labels)
- Time periods (as cycles)
As much data as possible is preserved when importing these entities Workpath, but due to differences in data models between the two applications, data will not look exactly the same – see below for an example as well as differences.
Consider loading your Viva Goals data onto a sandbox instance, i.e. a Workpath test instance for understanding what Viva data will look like. Your Client Success Manager can assist with this.
To create an export, perform the following steps with a Viva Goals administrator:
- Go the Admin dashboard, available in the navigation to the left of your screen.
- Select "Export".
- Choose "CSV", and click "Export".
- After some time (up to one hour), you should receive a link to download the export via email.
- Download the ZIP file, and share this file with your Workpath Client Success Manager securely, for example as a password-protected ZIP file.
If you have multiple Viva Goals organizations, repeat this step for each one, and discuss with your Client Success Manager how your organization should be structured in Workpath (several Workpath instances? Business Units?).
Step 3: Set Up Integrations (Optional)
Maximize the potential of Workpath by integrating it with other tools your team uses daily. Workpath excels when used in conjunction with the following integrations:
- Microsoft Teams Integration: Effortlessly view and update OKRs within Microsoft Teams without switching platforms.
- Jira Cloud & Data Center, Azure DevOps, and Microsoft Planner: Synchronize initiatives seamlessly to streamline project management.
For detailed instructions on configuring these integrations, please refer to the respective articles:
- Configure MS Teams Integration
- Configure Jira Integration
- Configure Azure DevOps Integration
- Configure Microsoft Planner Integration
If you have any questions or need further assistance, our support team is here to help. Please contact us at support@workpath.com.
Example
The following screens show example data in Viva Goals, and its representation in Workpath.
Differences between Viva Goals and Workpath
- Multiple Team / Outcome owners: Workpath supports only one owner per Team or Goal, so if there were multiple owners in Viva Goals, the first listed owner was migrated.
- Multiple Teams: The same applies to Goals, Key Results or Initiativies which were assigned to multiple Teams – they were imported only for the first of those teams.
- Automatic updates from integrations: If your Key Results can be updated from an Excel Online file, or a Power BI dashboard, see our documentation on how to establish that link. Automatic updates could unfortunately not be restored from Viva Goals data.
- Progress calculations from children: Not all progress automations from Viva Goals are possible to replicate in Workpath. Notably, Workpath does not support nesting Key Results directly under other Key Results, and cascading progress updates. Such Key Results were imported with their most recent progress value, but updates have to be done manually in Workpath.
- Time periods: Time periods are called "cycles" in Workpath. The most notable differences are: In Workpath, all Key Results under a Goal share the same cycle as the Goal. And when you navigate to a team, Goals from different cycles are shown in a list in addition to being nested under each other.