Org Units: Post-Migration Client QA Checklist

A QA checklist to complete after migrating your site to Org Units.

OVERVIEW

After migrating your site to Namely's Org Units feature, the same set of Org Units can be used across Namely HCM and Payroll, and updates made in HCM are automatically reflected in Payroll—eliminating the need for duplicate entries.
We recommend performing a quality assurance check of your site's Org Units post-migration to familiarize yourself with the new structure and functionality and ensure everything is set up properly. You can use the Post Migration QA Checklist embedded in this article to complete that audit.
We also recommend checking out the articles in the Also See section to learn more about Org Units and how it works.

POST-MIGRATION QA CHECKLIST

Refer to this article to have more information: Post-Migration QA Checklist

GENERAL TIPS AND REMINDERS

The way you manage your employees will change post-migration, here are some general reminders to keep in mind once your account has been migrated. 

  • Terminations are only managed within HCM. 

  • Employee Assignments are only managed in HCM. 

  • If you use payroll, Class changes and updates are only managed in HCM and they will flow into payroll automatically. 

  • There is no need to end-date a terminated employee’s org units assignments. The termination wizard will automatically assume those are end-dated based on the general termination date even if you don’t see a termination date next them. 

    • End-dates under the employee assignments (Org Units & Teams) cannot be removed. If you need help with this process, please contact your Service Pod for assistance. 

  • Percent Allocations are not automatically enabled post-migration. If you wish to have percent allocations activated, please contact your Service Pod for assistance. 

    • Once Percent Allocations have been activated, they cannot be deactivated at the company level. 

  • The names of Default Org Types will now show in the plural instead of the previous singular. For example, Division will now be Divisions, etc. This is important if you have a third party vendor integration setup that pulls data at that level.

  • Employee data will only be available/visible to restricted roles (non-Admin roles) until after the employees’ start date. 

    • In order to allow visibility to up-coming new hires’ data to non-Admin roles, an Admin can change the new hires’ org units’ start date to a current date (not in the future) under the Employees’ Org Units & Team tab.

  • Only Default Org Types show on the Analytics tool, Custom Org Types only show under the default Reporting tool within HCM. 

    • Custom Org Types also do not flow into payroll.