---
title: "How Workday data conversion works — Kiweely"
description: "Workday data conversion: map legacy fields, load with an EIB or connector in an implementation tenant, validate, fix and reload. Why it takes several cycles."
url: https://kiweely.com/guides/ai-workday-data-conversion-mapping
---

# How Workday Data Conversion Works, and Why It Takes So Many Loads

Legacy data reaches Workday through inbound integrations such as EIB, loaded and checked in implementation tenants first. Here is the cycle, why it repeats, how to map it, and one worked EIB load.

-   **Checked** against Workday on November 19
-   Applies to **Workday Extend**
-   11 min read
-   Published November 16
-   By Kiweely

Data conversion in a Workday implementation moves your legacy data (workers, organizations, cost centers, balances, history) into Workday through inbound integrations, most often an EIB (Enterprise Interface Builder) loading a spreadsheet, or a connector. Each load is run and checked in an implementation tenant first: Workday describes implementation tenants as the place for loading legacy data, alongside testing integrations and unit and end-to-end testing. Workday’s deployment guide puts data conversion in the architect and configure stage, and converting production data in the deploy stage, at go-live.

**Kiweely Vine** is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect: it cleans legacy sheets, builds the EIBs and loads and checks them in the tenant. See how it works below.

The cycle for each object is the same: map the legacy fields to Workday’s, clean the source, generate the load file, validate it, load it, read the result back, fix what failed and load again.

## Why it takes so many iterations

-   **The source isn’t clean.** Legacy extracts carry duplicates, closed records, mixed date formats and codes that mean different things in different places. Each problem found in a load sends the file back to the people who own the data.
-   **Order matters.** A row can only load when the objects it points at already exist: the company, the location, the supervisory organization. One missing parent fails every row that depends on it.
-   **The configuration is still moving.** In the architect and configure stage, the design changes as workshops make decisions, so a file that loaded last month can fail against this month’s configuration.
-   **The data goes in more than once.** Workday notes that customers may have several implementation tenants, and production data is converted again at go-live, so a file that loaded once has to load cleanly again in each place.
-   **“Completed” isn’t “correct.”** A load can finish with rows in error, or load rows that are wrong. Someone has to read the data back where the business would see it.

Workday gives you a dry run for the load itself. On an EIB’s launch screen, **Validate Only Load** with **Add Errors to Attachment** tests the integration without modifying any data in your tenant, and writes comments on the rows that failed so you can fix them in the spreadsheet. That shortens a cycle. It doesn’t remove the mapping, the cleaning or the business questions.

Workday has **not** published an AI product that maps a legacy spreadsheet to Workday fields. Deployment Agent can explain a load and interpret a SOAP fault in a non-Production tenant. The mapping is still a table a person owns, and the load is still an integration you launch.

Metadata is Workday’s and you cannot change it. Tenanted data is your configuration and the data you add.

## One worked example: a messy cost-center list, loaded by EIB

In a [recorded run](https://youtu.be/o1lMLI_Pbsc) in Kiweely’s own Workday Development tenant, Kiweely Vine, the desktop AI agent for Workday consultants, was given a messy cost-center spreadsheet and asked to load it. Before building anything it listed what was wrong with the source: mixed date formats, inconsistent codes, a repeated line, closed and “do not load” rows, subtotals and blank rows. It asked only the business questions (what to do with the closed rows, which line to keep), and the consultant approved the cleaned list. Kiweely then built the EIB and loaded it. Workday reported 18 processed, 18 loaded and 0 failed. The whole recorded session, including first-use setup and checks, took 97 minutes. The [write-up of the same run](https://kiweely.com/blog/messy-spreadsheet-eib) shows the file and the result.

Be clear about its size: that is one object and 18 rows, not a worker conversion with job, compensation and history across several tenant builds. It shows the cleaning and the questions moving off the consultant’s hands, not a conversion programme finishing early. For the EIB steps themselves, see [what an EIB is and how to load one](https://kiweely.com/guides/what-is-an-eib-in-workday).

## Separate three moves people call “conversion”

| Move | Tool Workday documents | What it will not take |
| --- | --- | --- |
| Configuration from one Workday tenant to another | Object Transporter, including dependencies of the objects you select | Transactional data and reference data. Workday’s example: a report migrates with its calculated field, not with the location the field points at. The location is a missing prerequisite you create or map on the target. |
| Workday-provided sample content into an implementation or sandbox tenant | Configuration Catalog, migrated with Object Transporter | Your legacy workers, journals, or balances. Catalog content is sample reports, dashboards, integrations, condition rules and calculated fields with minimal tenant-specific information. |
| Data from a legacy system into Workday | An inbound integration. Prefer a connector template when one fits; otherwise Orchestrate, document transformation, or Studio, in the order below. Enterprise Interface Builder is the wizard for a simple inbound or outbound. | A configuration package. EIB is not Object Transporter. |

Object Transporter also assumes two instances with the same Reference ID and Reference ID type are the same object. Set parent and child Reference IDs before the first migration, unique across tenants. **Integration IDs** shows current values. **Maintain Reference IDs** changes them in bulk.

## Pick the inbound tool in Workday’s order

The integrations course tells you to choose inbound tools in this order:

| Try this first | When |
| --- | --- |
| End-to-end connector | A template matches the vendor file and you do not need to transform it. |
| Generic connector (Core Connector) | A template has the elements you need, and the file is XML or CSV. |
| Orchestrate | No package fits. You need events or batches, a transformation, or a call to Workday or a third party. |
| Connector with Document Transformation | You must reshape an XML file to Workday’s format and you need your own error or warning messages. |
| Workday Studio | Many web-service requests per object, one-by-one processing, or complex errors and logging. |

Connectors call SOAP for you. You write SOAP or REST yourself when you use Studio. Studio can also use RaaS and WQL. A custom report becomes a web service when you enable it as a web service. The course calls that Report-as-a-Service.

EIB, in the financial-accounting course, is the wizard for simple inbound and outbound integrations. An EIB has three parts: **Get Data** (where the file comes from, or the report you extract), **Transform**, and **Delivery**. Inbound examples include a spreadsheet attached at launch, a REST URL, or a file from an external server. The journal pattern is: create the EIB, generate the spreadsheet template, fill it, launch, and verify. Outbound EIBs do not export Excel. Export CSV and open that in Excel.

For a large lookup table, Workday’s advanced-lookup example uses an inbound EIB with web service operation Put Advanced Lookup Table, a generated spreadsheet with data, and **Launch / Schedule Integration** to load the edits.

## A mapping table that matches how loads fail

Build the crosswalk before the first file. One row per legacy column.

| Column | What to write | Why it fails without it |
| --- | --- | --- |
| Legacy field | The source column name, unchanged | Two people will “fix” the same column differently. |
| Workday object and field | The business object and the field or web-service element | “Department” is not a Workday field name. |
| Reference ID type and value | The ID the load and Object Transporter will treat as identity | A missing or mismatched Reference ID stops a migration prerequisite check. A load that invents a second ID creates a second object. |
| Prerequisite object | The parent that must already exist (company, location, supervisory organization, ledger account) | Object Transporter will not create the location a report depends on. A web service often fails the same way, sometimes on the parent element. |
| Transform | Code map, date format, or “reject” | Connectors and EIB transforms are where this belongs, not in a one-time paste. |
| Sample row you have opened in the tenant | One real ID you can find with search | An agent’s field name that you cannot open is not a mapping. |

### Use Ask on the fault, not on the whole file

Workday’s published troubleshooting prompt is a SOAP error while migrating Payroll data with Object Transporter. The worked SOAP example is Submit\_Expense\_Report returning “Validation error occurred. The field Expense\_Report\_Data is required” even though that element is present. Workday’s point: the fault can name a parent when a child element or a security requirement is what is missing. Paste the fault, say what you already verified, and ask which functional area and domain the integration system user needs.

That prompt belongs in the Implementation or Sandbox tenant where the load failed, with Ask enabled, or in Customer Central with the tenant named. It does not fill the spreadsheet. After you change security, activate pending security policy changes. After you change the file, launch again and read the integration event. The agent does not launch it.

CRAFT still applies: context (Financials, this tenant), role (integration consultant), action (explain this fault), format (the missing child elements and the domains), tone (for the person who will edit the file).

## Payroll history is a dated decision, not a mapping trick

The payroll framework course documents **Override First Processing Period** on the pay group. Use it for the first period Workday Payroll will calculate, and, for payroll consultants, the initial period for parallel testing. On a mid-year go-live, load history for periods before go-live, then set the override to the first period Workday will process, the period after the last historical period. The course’s example is an April go-live on a monthly calendar: select the April period. That is the published rule. It is not a license to load history into the period you will also calculate.

## Failure modes

| Symptom | Likely published cause |
| --- | --- |
| Object Transporter lists a missing prerequisite | No matching instance on the target, or the Reference ID is missing or does not match. Resolve the first 50 before the rest appear. You can map a source instance to a compatible target instance in the workflow. |
| The diff shows Modified, and security changed more than you expected | For ordinary instances, migration overwrites the target with the source. Security policies merge unless you change that behavior. Migrating a security group and its business process security policy permissions is additive; it does not remove existing groups. |
| The EIB “worked” and the numbers are wrong | Verify the launch. Generating a template is not a load. Outbound Excel is not a format Workday’s EIB course offers. |
| Ask invented columns | It can be incomplete. Keep a column only if you can see the field or the web-service element in the tenant or the WSDL material the agent cites. |
| The only crosswalk was in the chat | Chat history is deleted after 14 days. |

## Watch Kiweely Vine build and load an EIB

![Workday's execution summary for the cost center EIB Kiweely Vine loaded: 18 records processed, none failed](https://kiweely.com/guides/ai-workday-data-conversion-mapping/media/vine-eib-cost-centers-d2a43dc234d0.webp)

From the film: 18 records processed, none failed.

Kiweely Vine takes a messy cost center spreadsheet, lists its problems, asks only the business questions, builds the EIB on Workday’s own template and launches it in a Workday Development tenant. Workday reports 18 processed, 18 loaded, 0 failed. 97-minute recorded run, first-use setup included.

[Watch the film (13 min)](https://www.youtube.com/watch?v=o1lMLI_Pbsc) · [Start for free](https://kiweely.com/sign-in?intent=signup)

## Frequently asked questions

### Can Deployment Agent generate the mapping workbook?

It can suggest steps and interpret a fault for a named tenant. Workday does not describe it as a mapping engine. The crosswalk has to live in your project record.

### Should we migrate workers with Object Transporter?

Object Transporter migrates configuration and dependencies, not transactional or reference data. Worker and transaction loads belong on an inbound integration. Check **Object Transporter Supported Objects (OX)** before you promise a configuration object will migrate.

### Which tenant do we load first?

An Implementation tenant. Workday names legacy data loads as one reason those tenants exist. Prove one file there, then decide what is configuration (Object Transporter) and what is data (the integration).

### Do we need Studio because the file is messy?

Only after you have walked the inbound order. A vendor template or a generic connector avoids a custom assembly. Studio is for multiple requests per object, row-by-row processing, or error handling the connector path does not cover.

## Where Kiweely fits

**Kiweely Vine** is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect. It cleans source sheets, builds EIBs, loads them and reads back the records in your tenant.

In a recorded run in Kiweely’s own Workday Development tenant (with fictional sample data, not a customer result), Vine read a messy cost-center spreadsheet, flagged its problems (mixed dates, inconsistent codes, a repeated line, closed and “do not load” rows, subtotals and blanks) for the consultant to approve, built the EIB and loaded the cleaned list: **18 processed, 18 loaded, 0 failed** in a 97-minute recorded session ([watch the film](https://youtu.be/o1lMLI_Pbsc)).

Vine Free is $0 on a personal developer tenant with $5 of Kiweely Credits included, and Vine Personal ($99/month) and Vine Team ($149/seat/month) connect to any Workday tenant ([pricing](https://kiweely.com/pricing)). [Start free](https://kiweely.com/download).

## Sources checked

Public Workday course and admin-guide topics and Workday’s deployment guide, listed above, checked again on 2026-11-17. No page checked describes an AI data-mapping product. The worked example is Kiweely’s own recorded run in its Development tenant with sample data, not a customer result.

## Sources checked

-   [Workday Tenants and Tools](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-for-administrators/workday-tenants-and-tools.html)
-   [Accounting Journals](https://doc.workday.com/workday-education/en-us/course-manuals/financial-accounting-for-administrators/accounting-journals.html)
-   [Workday Integrations Overview](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/workday-integrations-overview.html)
-   [Concept: Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/omh1634567473070.html)
-   [Concept: Reference ID Management for Object Migration](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/hug1453489539261.html)
-   [Maintain Career Paths Using the Put Company-Defined Career Path EIB](https://doc.workday.com/admin-guide/en-us/human-capital-management/talent/career-hub/maintain-career-paths-using-the-put-company-define.html)
-   [Workday: Your Ultimate Guide to a Successful Workday Deployment](https://forms.workday.com/content/dam/web/en-us/documents/other/deployment-strategies-guide-enus1.pdf)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### The 2026 Workday AI map: Sana, ASOR, Workday-built, custom, partner, and external agents Workday’s public AI story has five layers: Sana orchestrates, ASOR governs, Workday-built agents ship in the product, partners and customers bring their own, and build tools such as Developer Agent create new ones. This guide places each layer with Workday’s own words.](https://kiweely.com/guides/workday-ai-ecosystem-map-2026)
-   [### What Workday’s Deployment Agent Can and Cannot Do in Your Tenant Workday’s ASOR-enabled Deployment Agent reads tenant configuration in Implementation, Sandbox, Preview and Customer Central. It doesn’t run in Production, and edits configuration only in partner early access. Workday publishes no price; the Rate Card meters 5 credits per Ask interaction.](https://kiweely.com/guides/workday-deployment-agent-tenant-inspection)

### More guides on More Workday guides

[All 46 guides](https://kiweely.com/guides#more)

-   [Pre-Hire Windows That Create Directory Users Before Anyone Is Hired](https://kiweely.com/guides/pre-hire-windows-that-create-directory-users-early)
-   [Why Workday to Microsoft Entra Incremental Sync Misses Changes](https://kiweely.com/guides/why-workday-to-entra-incremental-sync-misses-changes)
-   [Remap Workday Benefit Codes When a Carrier Companion Guide Changes](https://kiweely.com/guides/remap-workday-834-codes-after-companion-guide-change)
-   [Full File or Changes-Only 834 After Workday Open Enrollment](https://kiweely.com/guides/workday-834-full-file-or-changes-only-after-open-enrollment)
-   [Match Workday People to Okta on the ID That Survives the Job Change](https://kiweely.com/guides/match-workday-workers-to-okta-on-the-right-id)
-   [Why a Delivered Workday File Was Still Rejected](https://kiweely.com/guides/workday-file-delivered-carrier-rejected-rows)
-   [Scoping AI Workday Access for Contingent Workers and Alumni](https://kiweely.com/guides/scoping-ai-workday-access-contingent-workers-alumni)
-   [Correlating Workday Audit Events with AI Assistant Tool Calls](https://kiweely.com/guides/correlating-workday-audit-with-ai-assistant-calls)

### From the blog on More Workday guides

[All posts](https://kiweely.com/blog)

-   [Versioning and Rollback for AI-Built Employee Screens](https://kiweely.com/blog/versioning-rollback-ai-built-employee-screens)
-   [Which Coming-Next Product to Register For First](https://kiweely.com/blog/which-kiweely-product-to-register-for-first)
-   [Turning Failed AI UI Runs into Workday Tickets Clients Accept](https://kiweely.com/blog/failed-ai-ui-runs-into-workday-tickets-clients-accept)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
