You are here:
Migration FAQs
Review common questions about migrating from Work.com to HR Service, including feature parity, licensing, phased rollout support, and data model behavior.
- Why should I migrate?
HR Service represents a comprehensive redesign of Work.com. By migrating, you can unlock a unified employee experience with strong functional parity for core workflows. This includes moving to modern features like the Unified Employee Portal, HR Service Desk, Agentforce Agents, and an integrated Service Catalog , all while leveraging an updated and robust data model.
- Are all Work.com features available in HR Service?
This table compares current Work.com features with corresponding HR Service features.
Work.com and HR Service Feature Comparison Work.com Features Corresponding HR Service Features Employee Workspace (Portal) Unified Employee Portal Employee Concierge (HR Desk) HR Service Desk Employee Concierge Bot Agentforce Agents HR Service Center (Workflows & Approvals) Out-of-the-box Approval Workflows Employee Service Catalog Unified Catalog Shift Management Not Available Workplace Strategy Planner Not Available Digital Trust Cards Not Available Queue Management Not Available Wellness Check Not Available Broadcast Messaging Campaign Management (needs configuration) Legacy Employee data records -
Employee2 entity
-
Standard Person Accounts
-
- Can a Work.com customer buy AI Agent for Employee as a standalone SKU?
Yes. Customers can buy it as a standalone SKU. However, because this SKU uses the Agentforce User License (AUL), Work.com migration is not supported. As a result, new users must be created, and historical data (such as past cases) is not preserved. The migration tool is designed to prevent this data loss, which is why the LPP or LPS path is recommended.
- With which SKUs is Work.com migration available?
Work.com migration is available only with the Lightning Platform Plus (LPP) and Lightning Platform Starter (LPS) SKUs. To use HR Service features, customers must also purchase the AI Agent for Employee add-on.
- Is there a path possible to move an employee from PUL to UEL?
No. There is currently no direct path to move an employee from Platform User License (PUL) to Unified Employee License (UEL). The existing migration tool is designed for the Employee-to-Employee 2 data model migration and does not support license migration.
- What AddOn license is required to access the migration tooling?
To successfully set up, run, and manage the visual Data Processing Engine (DPE) migration tool, the following licenses are required:
- Admin Migration License: The admin user running the migration must have the EmployeeManagement Permission Set License (PSL).
- Prerequisite License Check: Ensure that your organization already possesses the underlying EmployeeManagementAddOn license.
- Is phased migration possible?
Phased migration is fully supported. The migration strategy is built explicitly on a dual data model strategy / data coexistence model. Because the new Employee2 records maintain a backend foreign-key lookup directly to your legacy Employee records , backward compatibility is preserved. Legacy Work.com objects remain completely intact and active , allowing you to safely transition users and operations in phases over time without disrupting existing business logic, reporting, or integrations.
- What happens to existing manager data and assignments?
Organizational hierarchy is preserved automatically. Manager assignments and updates for the new Employee2 records are completely handled by an integrated manager provisioning batch job.
- What happens to the existing Work.com data models?
Existing data architectures are preserved but isolated:
- Legacy Work.com objects are not restructured or overwritten.
- They remain intact as historical records, while HR Service exclusively uses the new Employee2-based data model.
- Will custom components work after migration?
No. Custom components do not work automatically after migration. Customers must replace deprecated Work.com features with supported HR Service features. For custom components, customers must test and validate post-migration behavior; in some cases, no equivalent replacement may be available.

