---
schema_version: "1"
id: 165681d5944f09340c6c26c8d5ed39e873a29e87b4909d26c10b9627c4aa494b
title: Implement a Work.com to HR Service Migration Approach
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/es_implement_your_migration_approach.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.es_implement_your_migration_approach.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 48687b438412f6f4998ef39cf8c373bbfb99608c718c20c4524c19615f0dd1f7
description: Implement a migration approach by using an existing Workday or custom MuleSoft integration, CSV import, or a custom implementation that uses Data Processing Engine, DBScript, or any job.
products:
  - Service Cloud
release: "264"
---
# Implement a Work.com to HR Service Migration Approach

Implement a migration approach by using an existing Workday or custom MuleSoft integration, CSV import, or a custom implementation that uses Data Processing Engine, DBScript, or any job.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=service.service_editions_reference.htm&amp;language=en_US" target="_blank">View supported editions</a>.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d121675e55">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d121675e55 ">To configure employee user settings:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d121675e55 ">Salesforce Administrator and Customer Community Plus Login User profiles along
              with the Employee Management user permission.</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d121675e55 ">To configure the Reports To field on the Person Account object:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d121675e55 ">HrServiceWorkspaceHrPsnl</td>

          </tr>
        </tbody>
      </table>

As a prerequisite, enable the Person Accounts object to make the Reports To field available in the org. The Reports To field is mandatory in HR Service. See [Enable Person Accounts](https://help.salesforce.com/s/articleView?id=sales.account_person_enable.htm&type=5&language=en_US).

You can implement one of these migration approaches.

- Approach 1: Retain the same person account records from Work.com and create employee2 and user records in HR Service. For this approach, make sure that Work.com and HR Service are on the same org.
- Approach 2: Create employee2, person account, and user records in HR Service. This approach works irrespective of whether Work.com and HR Service are on the same or different orgs.

The implementation process described here offers a logical flow to assist you with the Work.com to HR Service migration. Treat the information as a guideline rather than a definitive design, template, or solution. The process is applicable to standard Work.com configurations. It doesn't apply to customizations within Work.com.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/images/icon_note.png)

Note This isn’t an exhaustive list of migration tasks, but it covers the essential ones.

1. Configure employee user settings.
    
    During migration, the employee user settings are used to create the user records in HR Service. The HR Service user settings are identical to the existing Work.com user settings. So, create these org values that are similar to the Work.com employee user settings: Employee2UserProfileId, Employee2UserEmailEncoding, Employee2UserPermsetId, and Employee2UserDomainName. See [Provision Users with Required Profiles and Auto-Create User Records](https://help.salesforce.com/s/articleView?id=service.es_provision_users_and_auto_create_user_records.htm&language=en_US).
2. For approach 1, create employee2 records and link them to the existing person account records. For approach 2, create employee2 and person account records.
3. Update the Reports To field in the Person Account object.
    
    The Reports To field is similar to the Manager field in Work.com. See [Configure the Reports To Field on Person Account](https://help.salesforce.com/s/articleView?id=service.es_configure_the_reports_to_field_on_person_account.htm&type=5&language=en_US).
4. Create user records.
5. To make sure that employees can access their case, service catalog request, and other records after migration, update the records with new user IDs as required in approach 1. In approach 2, update the records with the new user IDs, account IDs, and contact IDs as required.
6. For approach 2, after the migration, deactivate the old user IDs and delete the employee and person account records in Work.com.
7. Uninstall the Work.com package.