You are here:
Work.com to HR Service Migration Approaches
Follow a migration approach that suits your scenarios and organizational needs.
Required Editions
| View supported editions. |
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
| Pros | Cons |
|---|---|
|
Consistency in references 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. |
Inability to use the existing person account records during migration Users may not be able to use the existing person account records in Work.com during the migration phase, which may interrupt business processes. |
|
Minimal changes to dependent components The standard and custom components and processes dependent on the Person Account object continue to operate in HR Service with little to no modification. |
Longer downtime Users sometimes face significant downtime of HR Service during updates to Employee2 and User objects, which can disrupt normal operations. |
|
Insufficient time to complete ongoing processes 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. |
Pros and Cons of Approach 2: Create Employee2, Person Account, and User Records
| Pros | Cons |
|---|---|
|
Undisturbed existing workflows 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. |
Additional effort for creating and updating objects 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. |
|
Shorter downtime Operating Work.com and HR Service independently minimizes downtime, enabling the migration to proceed with minimal impact on the current operations in Work.com. |
|
|
Sufficient time to complete ongoing processes The migration doesn’t impact existing Work.com functionalities and provides enough time to complete the ongoing requests or processes in Work.com. |
