---
schema_version: "1"
id: 7b94f4ce24d890d913197b2d09d0e324a22b717d3f0eefd7465020ea746f425e
title: Migration FAQs
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/hr_svc_migration_faqs.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.hr_svc_migration_faqs.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 854646f5b8c7003e1754c72b2a4863558bbf4e5f0680022f48c87d6f3b52de13
description: Review common questions about migrating from Work.com to HR Service, including feature parity, licensing, phased rollout support, and data model behavior.
products:
  - Service Cloud
release: "264"
---
# 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.
    
    <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small " summary="Work.com and HR Service Feature Comparison">
          <caption>Work.com and HR Service Feature Comparison</caption>
          <colgroup>
            <col style="width:50%">
            <col style="width:50%">
          </colgroup>
          <thead class="slds-text-title_caps ">
            <tr class="">
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d92138e55">Work.com Features</th>
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d92138e58">Corresponding HR Service Features</th>
            </tr>
          </thead>
          <tbody>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">Employee Workspace (Portal)</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">Unified Employee Portal</td>

            </tr>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">Employee Concierge (HR Desk)</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">HR Service Desk</td>

            </tr>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">Employee Concierge Bot</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">Agentforce Agents</td>

            </tr>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">HR Service Center (Workflows &amp; Approvals)</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">Out-of-the-box Approval Workflows</td>

            </tr>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">Employee Service Catalog</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">Unified Catalog</td>

            </tr>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">Shift Management</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">Not Available</td>

            </tr>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">Workplace Strategy Planner</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">Not Available</td>

            </tr>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">Digital Trust Cards</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">Not Available</td>

            </tr>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">Queue Management</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">Not Available</td>

            </tr>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">Wellness Check</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">Not Available</td>

            </tr>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">Broadcast Messaging</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">Campaign Management (needs configuration)</td>

            </tr>
            <tr class="">
              <td data-label="Work.com Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e55 ">Legacy Employee data records</td>

              <td data-label="Corresponding HR Service Features" class="slds-cell-wrap" style="vertical-align:top;" headers="d92138e58 ">
                <ul>
                  <li>
                    <p>Employee2 entity</p>
                  </li>

                  <li>
                    <p>Standard Person Accounts</p>
                  </li>

                </ul>
              </td>

            </tr>
          </tbody>
        </table>
- **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.