---
schema_version: "1"
id: 3fe044247c7d4bc1a15ae07093a2db956e4cc3e9841d3b5a5e9553b94969d84c
title: Work.com to HR Service Migration Approaches
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/es_migration_approaches.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.es_migration_approaches.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a4bbed6a0406bd992453cd676b9b2316e053140aee0f47533cca6e51de6cbe64
description: Follow a migration approach that suits your scenarios and organizational needs.
products:
  - Service Cloud
release: "264"
---
# Work.com to HR Service Migration Approaches

Follow a migration approach that suits your scenarios and organizational needs.

### 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>

Follow 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.

Each approach has its pros and cons.

## Pros and Cons of Approach 1: Retain Old Person Account Records and Create Employee2 and User Records

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <thead class="slds-text-title_caps ">
          <tr><th class="slds-cell-wrap" scope="col" id="d39535e67">Pros</th>
          <th class="slds-cell-wrap" scope="col" id="d39535e70">Cons</th>
        </tr></thead>
        <tbody><tr class="">
          <td class="slds-cell-wrap" data-label="Pros" headers="d39535e67">
            <p dir="ltr">Consistency in references</p>
            <p>Retaining the same person account records preserves the existing references to person
              account IDs and person contact IDs of the case and service catalog request records in
              HR Service.</p>
          </td>
          <td class="slds-cell-wrap" data-label="Cons" headers="d39535e70">
            <p dir="ltr">Inability to use the existing person account records during migration</p>
            <p dir="ltr">Users may not be able to use the existing person account records in
              Work.com during the migration phase, which may interrupt business processes.</p>
          </td>
        </tr>
        <tr class="">
          <td class="slds-cell-wrap" data-label="Pros" headers="d39535e67">
            <p dir="ltr">Minimal changes to dependent components</p>
            <p dir="ltr">The standard and custom components and processes dependent on the Person
              Account object continue to operate in HR Service with little to no modification.</p>
          </td>
          <td class="slds-cell-wrap" data-label="Cons" headers="d39535e70">
            <p dir="ltr">Longer downtime</p>
            <p dir="ltr">Users sometimes face significant downtime of HR Service during updates to
              Employee2 and User objects, which can disrupt normal operations.</p>
          </td>
        </tr>
        <tr class="">
          <td class="slds-cell-wrap" data-label="Pros" headers="d39535e67">&nbsp;</td>
          <td class="slds-cell-wrap" data-label="Cons" headers="d39535e70">
            <p dir="ltr">Insufficient time to complete ongoing processes</p>
            <p dir="ltr">Ongoing processes in Work.com, such as service catalog requests and
              approvals, fail because of insufficient time to complete them. These processes may not
              exist or exist differently in HR Service.</p>
          </td>
        </tr>
      </tbody></table>

## Pros and Cons of Approach 2: Create Employee2, Person Account, and User Records

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <thead class="slds-text-title_caps ">
          <tr><th class="slds-cell-wrap" scope="col" id="d39535e142">Pros</th>
          <th class="slds-cell-wrap" scope="col" id="d39535e145">Cons</th>
        </tr></thead>
        <tbody><tr class="">
          <td class="slds-cell-wrap" data-label="Pros" headers="d39535e142">
            <p dir="ltr">Undisturbed existing workflows</p>
            <p dir="ltr">The creation of person account, employee2, and user records makes sure that
              the existing workflows in Work.com remain unaffected, helping HR Service run alongside
              Work.com. The new records ensure continuity of business processes.</p>
          </td>
          <td class="slds-cell-wrap" data-label="Cons" headers="d39535e145">
            <p dir="ltr">Additional effort for creating and updating objects</p>
            <p dir="ltr">This approach requires the creation and updating of the Employee2, Person
              Account, and User objects in HR Service, which can be time-consuming and
              resource-intensive.</p>
          </td>
        </tr>
        <tr class="">
          <td class="slds-cell-wrap" data-label="Pros" headers="d39535e142">
            <p dir="ltr">Shorter downtime</p>
            <p dir="ltr">Operating Work.com and HR Service independently minimizes downtime,
              enabling the migration to proceed with minimal impact on the current operations in
              Work.com.</p>
          </td>
          <td class="slds-cell-wrap" data-label="Cons" headers="d39535e145">&nbsp;</td>
        </tr>
        <tr class="">
          <td class="slds-cell-wrap" data-label="Pros" headers="d39535e142">
            <p dir="ltr">Sufficient time to complete ongoing processes</p>
            <p dir="ltr">The migration doesn’t impact existing Work.com functionalities and provides
              enough time to complete the ongoing requests or processes in Work.com.</p>
          </td>
          <td class="slds-cell-wrap" data-label="Cons" headers="d39535e145">&nbsp;</td>
        </tr>
      </tbody></table>

Select an approach after evaluating your use cases and the complexity of your Work.com implementation.