Reference: Solutions Migration and Sharing Limits

If the Weekly Service Update for your tenant is on Wednesday, you can’t perform these actions between Wednesday and the regular Weekly Service Update on Friday night:

Publish a Solution.
Migrate a Solution between tenants.
Browse for a Solution.
Request a Solution.
Import a Solution.

When migrating Solutions, you can't perform these actions:

Migrate Solutions from a Preview tenant.
Migrate Solutions from a non-Preview tenant to a Preview tenant.
Migrate Solutions from an Implementation tenant to a Production tenant. Workday doesn’t provide you with an option to select a Production tenant. Instead, migrate Solutions from Implementation tenants to Sandbox tenants. In your Sandbox tenant, review and test the Solution and your tenant. Then, migrate Solutions from Sandbox tenants to Production tenants.
Migrate Solutions from any tenant to an Implementation Gold tenant. Workday doesn’t provide you with an option to select a Gold tenant. Contact your implementation consultant for assistance.

Workday recommends that you migrate Solutions to or from any Implementation and Sandbox tenant only if it's a recent copy of the associated Production tenant. If you entered the data in both tenants either manually or using other implementation tools, don't migrate Solutions between tenants.

When you migrate a Solution, Workday updates any Configurations in the destination tenant that have the same Workday ID (WID) as the Configuration in the Solution. If the Configuration doesn't have a matching WID, Workday creates a Configuration.

When you migrate a Solution, Workday doesn't attempt to migrate data outside of the scope of the Solution. When Configurations within the Solution reference data outside of the Solution, Workday attempts to connect this relationship based on WID. For setup data, Workday attempts to connect the relationship based on Reference ID if matching by WID fails.

If you remigrate the Configuration, Workday attempts to add additional relationships, but doesn't delete existing relationships.

When you migrate effective-dated Configurations, Workday sets the effective date of each Configuration as of the moment that the Configuration migrates into the target tenant. This action prevents back-dated Configurations, especially Configurations related to business processes, from affecting:

In-progress business processes.
Scheduled report generation.
Other actions.

Workday doesn’t migrate or publish Solution configurations referenced by other Configurations as instance references. Example: if you migrate a custom report with a filter that references a business process definition as a comparison value, Workday doesn’t migrate the business process definition. To migrate instance references, you can manually add that Configuration to the Solution or create a Bulk Solution.

If you attempt to migrate a Solution that depends on objects that aren’t valid dependent Configurations, Workday displays an error and doesn’t migrate the Solution.

When importing or publishing Solutions, you can't perform these actions:

Don’t use the Publish Solution feature when you want to:

Migrate your data.
Back up your data (even temporarily).
Implement change management or version control.

If you attempt to import or publish a Solution that depends on objects that aren’t valid dependent Configurations, Workday:

Displays an error.
Doesn’t import or publish the Solution.