Workday Tenant 

A tenant is a unique instance of the Workday Service with a separate set of data held by Workday in a logically separated database (that is, a database segregated through password-controlled access). 

Tenants Used During Deployment

• Foundation Tenant
• End-to-End Tenant
• Parallel Tenant (if Payroll is in scope)
• Gold Tenant
• Production Tenant

Gather Data

• Data gathering means extracting data from the legacy systems and get it into the Workday tenant
• Multiple sets of data might need to be loaded depending on the scope of the deployment
• This could be setup data such as cost centers, regions, locations; or worker data like HCM employee data and benefit enrollments

Data Conversion

• There are some data points that can be viewed differently between Workday and the legacy system.
• Some of the data conversion activity might be to map legacy data to Workday terminology, configuration, and format

Number of Times Data Is Gathered and Converted

• Every tenant build provides a chance to update and provide data
• With each tenant load data will get cleaner with fewer validation issues and map better and become more accurate
• At the start of the project the first cut of setup and employment data is provided
• Fresh data will be extracted before the start of the End-to-End tenant build
• Fresh data will be extracted for the final time for the Gold build
• For financials, we like to include history conversion in at least one of the tenant builds before building the Gold tenant

Specific Data for Financials Deployments

• General Ledger balances, Business Assets, Suppliers, and customers
• Bank balances, Projects, Budgets, and open invoices might be needed

Amount of Data

• Current year for most data elements
• Depends on requirements, internal controls and rules, and scope