We recommend organizations to chose the deployment path that makes most sense for them depending upon following uses cases:
- For new customers — All new customers should deploy Employee Center or Employee Center Pro from the ServiceNow store. No new customer should deploy Service Portal (/sp).
- For organizations currently on Employee Service Center — They will be automatically upgraded to Employee Center Pro as part of their Rome upgrade. They will see the name change as part of the upgrade to Rome and will have to download the Employee Center Pro app from the store to get the latest functionality. With the San Diego upgrade, the November store release applications for Employee Center are automatically installed. This will not affect the current Employee Service Center deployment.
- For organizations currently on Service Portal (/sp) — These organizations will need to migrate to Employee Center to take advantage of the new capabilities and align with ServiceNow’s future investment in rich employee experiences.
For organizations, migrating from Service Portal (/sp) to Employee Center, we've covered an academy session covering following topics:
- How does Employee Center differ from Service Portal (/sp)
- Migration steps from Service Portal to Employee Center
- Live walk-through of creating an IT-only portal experience on Employee Center
Refer to this link for the session recording and slides on Migrating from Service Portal (/sp) to Employee Center.
For upgrading organizations, we've covered an academy session discussing best practice guidelines on how to Test, Deploy and Upgrade Employee Center in production:
- Working with Employee Center Applications Scopes
- Moving Employee Center changes to production
- Testing Employee Center
Refer to this link for the session recording and slides on how to Test, Deploy and Upgrade Employee Center.
