Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2025-10-17
Reference: Migration Implementation Tools

Reference: Migration Implementation Tools

Use the table to help you decide which implementation tool is best for your migration needs.

Implementation Tool
Primary Migration Use Case
Object Transporter (standalone)
  • Single instances
  • Configuration packages (also known as standard configuration packages)
  • Security configuration packages
Use Object Transporter directly (from the
Migrate with Object Transporter
 task or related action) to migrate specific configuration objects and their dependencies at once. It's the proven method for migrating isolated changes.
Use case examples:
  • Migate one or more custom reports.
  • Migrate specific business process definitions.
Benefits:
  • Includes every dependent component of an object, ensuring that your object migrates completely, even with complex dependencies.
  • For many, it's the most familiar migration tool.
Limitations:
  • Only supports objects listed in the
    Object Transporter Supported Objects (OX)
     report.
  • Less efficient for migrations of large projects with many unrelated changes.
Configuration Change Tracker
Use Configuration Change Tracker for project-based work.
Use case example:
Save project work for sandbox refreshes. In Configuration Change Tracker, create a configuration package of the changes you want to change in your tenant. Then, create a configuration extract of the package, download it locally until the tenant refresh completes, and reload the package to the refreshed tenant.
Benefits:
  • Captures a wide scope of work based on users and time, simplifying project migrations.
  • Supports all implementation types.
  • Easily enables you to save configuration changes in a Development or Sandbox tenant.
Limitations:
  • Doesn't add missing dependencies. If a user makes a required change in a timeframe other than that which you select, Workday doesn't migrate the change, potentially causing migration failures.
  • Requires a well-defined and disciplined development process to ensure that necessary changes are captured.
Configuration Extracts
Use configuration extracts when you need to store configurations externally from the tenant.
Use case examples:
  • Create offline backups of project work.
  • Share configurations with other teams.
  • Reload a configuration to the same tenant after a refresh.
    Start with Configuration Change Tracker and create a configuration package of the changes you want to change in your tenant. Then, create a configuration extract of the package, download it locally until a tenant refresh completes, and reload the package to the refreshed tenant.