---
title: "Workday cutover and go-live sequence — Kiweely"
description: "What happens at Workday cutover and go-live, in order, from Workday's own pages: migration with Object Transporter, data, payroll, checks and hypercare."
url: https://kiweely.com/blog/workday-cutover-runbook-from-ai-tests
---

# Workday cutover and go-live: the sequence, and a list written from tests

Workday’s Deploy stage covers training, go-live checklist sign-off, production data, stabilizing and handover to operations. Here is the sequence, checked against Workday’s pages, and how to write each line of the list from a record a test produced.

-   By Kiweely
-   November 16
-   Updated November 17
-   8 min read

Cutover is the last stretch of Workday’s **Deploy** stage. Workday’s deployment guide describes that stage as rolling out end-user training, signing off the go-live checklist, converting and configuring production data, making sure the deployment is stabilized, and moving to customer operations. The steps below are the order those things happen in, with each one checked against Workday’s own pages. Your partner’s cutover plan will add owners and times; the Workday tasks underneath are the same.

## The cutover and go-live sequence

1.  **Freeze the source configuration.** Object Transporter always migrates the *current* version of each object, so any edit made in the source tenant after the last rehearsal is what moves.
2.  **Give the people who migrate access to Production.** Customer Central needs access to the Production tenant (Set Up Customer Central Production Access), and anyone loading or migrating to Production first creates a Production tenant session, which links their Customer Central account to their own Production account. They also need a valid Production account with the right security permissions.
3.  **Migrate the configuration with Object Transporter.** Workday runs an error check, then a prerequisites check (resolve the first 50 listed before it shows more), then a Pre-Migration Diff Report. Read the diff: modified instances are overwritten, except security policies, which merge by default unless you choose to overwrite; a security group’s business process security policy permissions migrate additively, so any removals are a manual step.
4.  **Check what moved.** Open the post-migration summary (Workday keeps it for two years) and run a Tenant Compare report against the target, which checks Reference IDs and attributes instance by instance.
5.  **Convert and load production data.** Object Transporter moves configuration, not transactional or reference data. Workday’s own example: a report migrates with its calculated field, but the location the field references is flagged as a missing prerequisite. Data goes in through the loads you rehearsed, and each is verified after it runs.
6.  **Set payroll’s first period, if Payroll is going live.** On each pay group, Override First Processing Period is the first period Workday Payroll calculates; for a mid-year go-live it is the period after the last one loaded as history. Update it before calculating any payroll, because after the first calculation it can’t be changed.
7.  **Launch the inbound integrations you verified, and verify them again** from the integration events.
8.  **Sign off the go-live checklist, then open the tenant** with end-user training rolled out, as Workday’s Deploy stage describes.
9.  **Stabilize, then hand over to operations.** Hypercare works from Production records: business process events, integration events and the migration summaries. Workday’s Deployment Agent isn’t available as a conversational assistant in Production, so it isn’t part of hypercare.

Kiweely has not filmed a cutover, so this article makes no claim about an agent running one. Where an agent helps is earlier: in the tests whose records each line of the list should point at. For how those tests are run, read [testing in a Workday implementation](https://kiweely.com/guides/workday-implementation-testing); for where cutover sits in the whole timeline, [how long a Workday implementation takes](https://kiweely.com/guides/how-long-does-a-workday-implementation-take).

## A cutover list written from tests, not from a chat

Workday has **not** published a cutover runbook generator. The cutover list is yours. The parts Workday will actually execute are Object Transporter migrations, integration launches, and the business processes workers start in Production. An agent can help you write the list only where a test already produced a Workday record you can name.

Deployment Agent will not be in the Production room as a conversational assistant. If the list says “ask the agent if Production looks right,” the list is wrong.

## Write the list from records that outlive the chat

| Cutover action | Source of the line | Do not write this line from |
| --- | --- | --- |
| Migrate a configuration package to Production | A successful migration into the Implementation or Sandbox tenant, plus the diff you reviewed. To migrate to Production, the person running it needs a Production tenant session in Customer Central. | “The agent listed these reports.” |
| Expect a security group to be removed on Production | A manual step. Migrating a security group and its business process security policy permissions is additive. Existing target assignments stay unless someone removes them. | “The diff will revoke Production access.” It will not, by default. |
| Expect a security policy to be overwritten | An explicit Edit Migration Behavior choice. The default is to merge security policies. | A chat summary that said “security will match.” |
| Load legacy or inbound data | The integration system you launched and verified in the implementation tenant. | A generated spreadsheet template. Generation is not a load. |
| First payroll period Workday will calculate |  **Override First Processing Period** on the pay group, set to the first non-historical period. The payroll course’s mid-year example is the go-live period after the last period you imported as history, and it can’t be changed once payroll has been calculated. | A parallel-test story with no period named. |
| Confirm two tenants match after the move | A saved Tenant Compare: unmatched Reference IDs, attribute diffs, missing IDs. | A green sentence in a thread that Workday will delete in 14 days. |
| Hypercare a Production business process | The event in Production, the definition inheritance selected, Test Rule if a condition failed. | Deployment Agent chat. It is not available in Production. |

Post-migration summaries remain for two years. Put the summary name on the list. That is the artifact you will reopen when something on Production does not match the rehearsal.

## What an agent can add the week before

In the Implementation or Sandbox tenant, with Ask on, use a fresh chat per package. Prompt with the package’s actual fault or object, not “write my cutover plan.”

> I am an implementer. In my tenant, Object Transporter reported this SOAP error while migrating \[package\]. Here is the message: \[paste\]. What should I check before I retry? I will confirm each item on the pre-check page.

Then look at the pre-check page. Prerequisites are missing instances or Reference IDs that do not match, and only the first 50 appear. The list should name the IDs you cleared, not the agent’s theory.

> In my tenant, how does calculated field \[name\] work?

If that field is in the package, the cutover line is the field’s Reference ID and its prerequisites, especially reference data such as a location that will **not** migrate with the report. Workday’s example is exactly that: the report and the calculated field move; the location is a prerequisite.

[Kiweely Vine](https://kiweely.com/vine) can draft a document from the tenant you are signed in to and file it on the project. Use that draft as a checklist only after each line points at a package, an integration event, or a business process definition you have opened. Vine asks before it changes Workday. A document does not migrate a package. Kiweely’s copy also says Production stays yours on Extend promotions: the agent promotes through Sandbox, and a person still owns Production.

## Rehearse the sequence you will actually run

Workday’s migration order is the rehearsal order:

1.  Clear **View Errors**.
2.  Clear prerequisites, including Reference IDs, in batches of 50.
3.  Read the diff. Decide exclusions. Decide merge versus overwrite for security policies. Plan manual removals for groups that additive migration will not drop.
4.  Migrate. Workday moves the **current** version, not the version from the day you built the package. If someone edits the source the morning of cutover, that edit is what moves.
5.  Open the post-migration summary. Run Tenant Compare against the rehearsal target. Save it.
6.  Launch the inbound integrations you verified, and verify them again.
7.  Have one worker in the real security group start one business process whose definition you expect inheritance to select.

Do that against a non-Production target first. Production is the same tasks, not a new method. Migrating to Production also needs the Production tenant session from step 2 of the sequence above. Single-instance migration from Production is not supported; do not plan on pulling a single report back out that way during hypercare.

Configuration that must survive a Sandbox refresh in the weeks after go-live belongs in Production (so the refresh copies it) or in an extract you can reload. Deployment Agent’s own setup is the documented example: configure it in Production if you want Sandbox to keep it, and deactivate it in Production if you do not want a refresh to turn it on. The same refresh rule applies to every other configuration that lived only in Sandbox.

## Failure modes

-   A runbook that is a cleaned-up chat. No package names, no Reference IDs, no event IDs.
-   Assuming No Change on the diff means “we updated Production.” It means source and target already match. If Production is wrong, so is the source.
-   Leaving a prerequisite “for hypercare.” The migration will not proceed past the ones it is showing you.
-   Scheduling the agent as Production support. Bring the event, the integration event, and the post-migration summary. Bring people who can edit Production. The conversational agent will not be there.
-   Copying a desktop agent’s runbook into the bridge line without a person checking Reference IDs. The tool can write. Object Transporter decides whether the instance is the same one.

## Frequently asked questions

### Can we generate the runbook from passing agent tests?

You can generate a draft from tests that produced Workday records. A passing conversation is not a test. If there is no event, no integration launch, and no migration summary, there is nothing to cut over.

### Who runs the Production migration?

A person with access to the Customer Central tooling, on **Migrate with Object Transporter**, after the diff. Deployment Agent users are not automatically those people. The agent’s domain policy and the migration tooling are different setups.

### What do we do when Production fails at 2 a.m.?

Open the integration event or the business process event. Compare to the rehearsal summary. If the failure is configuration drift, Tenant Compare and the diff are the tools. There is no Production Deployment Agent chat to ask.

### Should the runbook include a Sandbox refresh?

Only as a hazard. A refresh replaces Sandbox with Production. It is not how you promote. Promoting is Object Transporter from the tenant that holds the rehearsed configuration, aimed at Production, after the checks above.

## Sources checked

Public Workday topics listed above, checked 2026-11-17. The payroll period control is from the payroll framework course fetched 2026-11-16. Vine’s document behavior is from kiweely.com. Workday does not publish an AI-generated cutover runbook on the pages checked.

## Read next

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

-   [November 16 ### Configuration workbooks are not a Workday object](https://kiweely.com/blog/ai-workday-configuration-workbooks)
-   [November 16 ### Fix the Workday Org Feed Behind a ServiceNow Ticket Storm](https://kiweely.com/blog/stop-servicenow-tickets-by-fixing-the-workday-org-feed)
-   [November 16 ### Day-One Access and Last-Day Revoke Without One Shared Account](https://kiweely.com/blog/day-one-access-and-last-day-revoke-without-one-shared-account)

### More guides on More Workday guides

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

-   [What Workday AMS Costs in 2026: Hourly Rates, Retainers and What They Cover](https://kiweely.com/guides/workday-ams-cost)
-   [Hire Another Workday HRIS Analyst or Add an AI Team? The Monthly Cost Compared for 2026](https://kiweely.com/guides/hris-analyst-or-ai-team-cost)
-   [Workday Configuration Catalog packages: filter, test, then migrate](https://kiweely.com/guides/workday-configuration-catalog-packages)
-   [How do I limit a Configuration Change Tracker package to a change window?](https://kiweely.com/guides/workday-configuration-change-tracker-time-bounded-packages)
-   [How do I build a Configuration Change Tracker package by user and time?](https://kiweely.com/guides/workday-configuration-change-tracker-how-to)
-   [Do You Need a Workday AMS Partner, or Can a Small In-House Team Run Workday?](https://kiweely.com/guides/workday-after-go-live-in-house-team)
-   [What Does a Workday Implementation Cost, and What Actually Drives It?](https://kiweely.com/guides/workday-implementation-cost)
-   [Set the Workday HCM foundation before you automate it](https://kiweely.com/guides/ai-workday-foundation-data-model)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

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

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
