Workday’s documentation describes two kinds of tools for this job: ones that move configuration (Object Transporter, Configuration Extracts) and ones that load records (EIB, web services, payroll and worker history loads). We found no documented feature that merges one tenant into another, so plan it as a configuration move plus a data load, rehearsed in an Implementation tenant first.
What kind of acquisition is this?
Ask this first, because it decides the tool.
| Situation | What it means for the move |
|---|---|
| SituationThe acquired company is already a Workday customer | What it means for the moveThere is a source tenant with configuration to read. Workday says to use Configuration Extracts when “your source and target tenants have different Billing IDs”, so check the Billing ID. |
| SituationThe acquired company uses another HR or payroll system | What it means for the moveNothing to migrate. Create its structures in your tenant and load its workers and history from legacy data. |
| SituationAsset purchase or merger of a US legal entity | What it means for the movePlan a successor employer company relationship for payroll taxes and W-2 reporting. |
What should you ask before you touch a tenant?
- Which legal entities are joining, with their tax IDs and countries? Workday recommends a company for every internal entity with a separate tax ID.
- Is the predecessor company already in Workday? If not, the company has to be created and its payroll history loaded.
- What is the first payroll date in the acquirer’s tenant, and what is the transfer date for workers?
- Which supervisory organization structure will the acquired workers land in, and is their staffing model job management or position management? Workday only lets you move workers between supervisory organizations with the same staffing model.
- Which security groups, roles and business process security policies from the acquired side should survive?
- Which integrations stay, which are retired, and who owns the integration system users?
- Which history is needed: job and compensation history, payroll year-to-date balances, or both?
- Is the Implementation tenant for the rehearsal available, and when is the next refresh planned for it? Workday refreshes Implementation tenants on demand.
What do you map, and with what documented tool?
| Area | What to map | Documented tool or task |
|---|---|---|
| AreaCompanies | What to mapOne company per entity with its own tax ID; contact, accounting and tax details; the USA company relationship if it applies | Documented tool or taskCreate Company (security: Create: Company domain); successor employer relationship for USA payroll |
| AreaSupervisory organizations | What to mapHierarchy, subtype, availability date, roles, organization assignments, reference IDs that do not collide with the acquirer’s | Documented tool or taskCreate Supervisory Organization; Create ID Definition / Sequence Generator and the Put_Organization_Reference_Id web service operation for bulk ID changes |
| AreaWorkers | What to mapEach worker into a company and supervisory organization on a transfer date | Documented tool or taskHire Employee or Import Hire Employee web service operations (the Staffing web service); Move Workers (Supervisory) or Move Workers (By Organization) to relocate workers already in the tenant |
| AreaSecurity | What to mapSecurity groups, domain and business process security policies | Documented tool or taskCreate Security Configuration Package with Object Transporter; Merge or Override when policies differ |
| AreaBusiness processes | What to mapDefinitions, steps, conditions, notifications; the Staffing processes the move needs | Documented tool or taskObject Transporter with the Business Process Definitions implementation type; configure Change Job and the Move Workers processes in the Staffing functional area |
| AreaIntegrations | What to mapIntegration systems, their ISUs and security groups, keys, supporting reports and processes | Documented tool or taskObject Transporter with the Integration Systems implementation type, plus the best practices below |
| AreaHistory | What to mapJob and compensation history from the previous system; payroll YTD and balances | Documented tool or taskPut Previous System Job History and Put Previous System Compensation History through an EIB; Prepare and Load Payroll History |
How should companies and supervisory organizations be handled?
Create a company for each separate tax ID with Create Company. For USA payroll, Workday’s successor employer feature continues payroll and tax reporting in the new company relationship. The relationship types are Asset Purchase - Alternate, Asset Purchase - Standard and Merger. Workday’s page says:
- For mergers and alternate asset purchases you must obtain the predecessor’s W-4 records.
- Create one relationship type per company per year, and set one Payroll Processing Begin Date for all workers in the companies.
- You cannot modify the relationship type once you have completed a payroll.
- Workers must be moved from the predecessor company to the successor company.
- If the predecessor is not in Workday, create the company and load its payroll history first.
For supervisory organizations, set the Availability Date and effective date deliberately, since the effective date decides when an organization becomes visible and roles can be assigned. Workday also warns of performance issues with more than 5,000 active workers in a single supervisory organization. If the acquirer already uses a reference ID format, create an ID definition so incoming organizations follow it.
How do security groups, business processes and integrations move?
Object Transporter moves configuration and its dependencies. It does not move reference data, so values the objects point to, such as locations or job profiles, have to exist in the target with matching Reference IDs. The Pre-Migration Check lists what is missing.
- Security. Create a security configuration package by choosing security groups, domain policies or business process security policies for a functional area. By default Workday merges: the source’s groups and roles are added to the target policies and nothing is removed. Override replaces the target policies, which suits initial deployments but is the wrong choice in an established acquirer tenant unless you mean it.
- Business processes. Add Business Process Definitions as an implementation type in the package. If an integration uses them, Workday says to include them in the package for the Integration Systems type.
- Integrations. Set up ISUs and integration system security groups in the target before migrating. Workday’s security model prevents PGP private keys from migrating, so create them in Production and refresh the tenant. X.509 key pairs between non-Production tenants use the Migrate X509 Private Key Pair task in Customer Central. Custom reports used by the integration go into the package too.
If the acquired company’s tenant has a different Billing ID, create a configuration extract from a Sandbox or Implementation tenant, download it, and load it into your Implementation or Sandbox tenant. Extracts cannot be loaded into Production.
How are history and workers loaded?
Worker records are data, so Object Transporter is not the tool. Workday’s Staffing web service includes the Hire Employee and Import Hire Employee operations, which an inbound integration can call.
For job and compensation history from the previous system, Workday offers an EIB loaded from Put Previous System Job History and Put Previous System Compensation History. Reference IDs can be your own or generated on upload. The security is the Worker Data: Historical Staffing Information domain plus the Integration domains for EIB.
For payroll history, Workday’s acquisition guidance says:
- In the USA, Australia, Canada and France, create a separate pay group for the acquired organization’s employees. Keep them there until the history has been checked, then move them to their permanent pay group.
- In the UK, test and reconcile the history in Sandbox Preview, then replicate it in Production.
- Load payroll history before recording that employees are terminated or on leave, so pay group reconciliation reports are complete.
- Load only the history that current calculations and reporting need. Workday recommends loading at least twice: into a test area, then live.
- Afterwards, check that each worker’s Period End Date falls after the Hire Date.
Worked example
A buyer using Global Modern Services as its model acquires a 40-person US company that has no Workday tenant. In the Implementation tenant they:
- Create the company with its own tax ID and set up the successor employer relationship as an Asset Purchase - Standard, with a Payroll Processing Begin Date equal to the worker transfer date.
- Create three supervisory organizations under an existing parent, using the acquirer’s ID definition.
- Hire the 40 workers through the Hire Employee web service operation and load job history on them with Put Previous System Job History.
- Load payroll history into a separate pay group, then reconcile it before moving workers to the buyer’s regular pay group.
- Migrate the buyer’s existing security and integration packages with Object Transporter where the acquired workers need the same access.
When each step has been read back, they repeat the same plan in Production, using a Customer Central Production session for the migration steps.
What stays with the people involved?
Several choices have no Workday answer: which of two security models wins, which integrations retire, and when each worker transfers. Settle them with the acquirer’s owners before any load, and write down the decisions alongside the Reference ID mapping so the Production run does not depend on memory.
Frequently asked questions
Can Object Transporter move an acquired company's workers into my tenant?
No. Workday says Object Transporter migrates configuration and dependencies, not transactional or reference data. Worker records are loaded as data, for example through the Hire Employee or Import Hire Employee web service operations, and history with the Previous System History loads.
Do I use Object Transporter or Configuration Extracts when the acquired company has its own Workday tenant?
Workday says to use Configuration Extracts when source and target tenants have different Billing IDs. Confirm the acquired company's Billing ID first. Extracts cannot be loaded into Production, so load into an Implementation or Sandbox tenant and move on from there.
Where should I rehearse an acquisition load?
In an Implementation tenant. Workday's tenant datasheet names M&A and divestiture scenario modeling as a use case. For UK payroll history after an acquisition, Workday recommends testing in Sandbox Preview before repeating the steps in Production.
How do acquired employees' prior-year wages count for payroll taxes in the USA?
Set up a successor employer company relationship (Asset Purchase - Standard, Asset Purchase - Alternate or Merger). It lets Workday use wages paid by the predecessor company for limits such as OASDI, Medicare, FUI and SUI.
Sources checked
- Datasheet: Workday Tenants
- Concept: Object Transporter
- Steps: Create Configuration Extracts
- Create Security Configuration Packages with Object Transporter
- Reference: Best Practices for Migrating Integrations with Object Transporter
- Steps: Set Up Companies
- Set Up Supervisory Organizations
- Automatically Generate Reference IDs for Supervisory Organizations
- Moving Workers by Organization
- Concept: Previous System History
- Setup Considerations: Payroll History
- Setup Considerations: Successor Employer Company Relationships (USA)