Why the Shift to Public Cloud?
Who Needs to Migrate, and When?
Some of the standout benefits:
Continuous use during updates – Even during weekly or monthly maintenance, users can remain active in the system.
How to Prepare for Migration
What can be expected
How Loop Consulting Can Help
Benefits open enrollment
Year-end processing
Merit cycles
Seasonal hiring
Major organizational changes, acquisitions, or divestitures
Planned add-on deployments (if you’re in an active deployment, aim to complete migration early in the process, ideally before end-to-end testing.
Select the Right Migration Dates. When choosing your migration window, avoid periods that overlap with critical business events, such as:
Align Stakeholders and Vendors. When choosing your migration window, avoid periods that overlap with critical business events, such as:
Implementation Tenant Migration
Leverage Your Test Implementation Tenant. . Workday will create a replica of your Production tenant in the destination Public Cloud data center for testing configuration changes and validating integrations.
Request Your Migration Window. . Submit a case via Customer Central to reserve your preferred migration date. Workday suggests notifying them at least six weeks in advance.
Migration Process Overview
Review and Sign the Public Cloud Migration (PCM) Document. This document formally records your intent to migrate, outlines post-migration configuration requirements, and offers the option to request a free test implementation tenant for up to two months. *Note: Signing the PCM doesn’t lock you into a migration date, it simply confirms your intent to move. Understanding which changes will immediately improve your workflows today, and which can wait, is what separates teams that stay reactive from those that get ahead of the curve. If you’re working through that prioritization now, you’re not alone. And if it would hep pressure-test what matters (and what doesn’t) in your tenant, a quick conversation can go a long way.
Occurs 1.5 – 2.5 weeks later, on a Saturday
Estimated downtime: up to 12 hours
Notifies all end users of expected downtime and new URLs

Outlines post-migration login or integration updates
The migration process follows two phases for most Production customers:
After both phases, Workday performs standard testing and releases your new tenants in the Public Cloud. Your old tenants are retained for 14 days as a contingency backup.
We strongly recommend developing a change management plan that:
Change Management & Communication
Production Tenant Migration
Our team can provide tailored templates, communication plans, and readiness assessments to minimize disruption.
Coordinates with external partners to validate data flows
Includes a post-migration validation checklist
Takes place on a Wednesday (Pacific Time)
Sandbox tenants are created as copies of the new production tenant after migration
Implementation and Customer Central tenants migrate first
Estimated downtime: up to 12 hours
As a Workday focused consulting partner, Loop Consulting has supported numerous clients through large-scale migrations and infrastructure changes. We can help you: Develop a migration readiness assessment and timeline, coordinate stakeholder and change management efforts, provide technical validation and testing assistance, and support post-migration optimization and configuration refinement. Whether you’re proactively planning your migration or waiting for Workday’s notice, Loop can help you navigate every step with clarity and control.