Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Use Case: Promoting UAT-Validated Changes to Production Using Incremental Migration

  • A previous Full Migration has been completed between the source (UAT) and target (production) organizations, establishing a baseline for Pricing objects and Workflow configuration objects.
  • You have access to both the source and target organizations.
  • Source and target organizations are validated in Migration Manager. For more information on how to validate the organizations, see Step 4 and Step 5 in Performing Incremental Migration.
  • The admin user in the target organization has permission to create or update data.
  • The target organization schema is aligned with the source. If schema differences exist, perform a Selective Migration to synchronize the schema before proceeding with incremental data migration.

Business Context:

An organization develops and validates configuration and data changes in a UAT environment before deploying them to Production. During testing cycles, new records are created, existing records are updated, and schema adjustments may be introduced.

After UAT validation, the business needs to promote only the approved changes to Production without:

  • Re-migrating unchanged data
  • Overwriting stable Production configurations
  • Causing unnecessary downtime
  • Running long Full Migrations

Incremental Migration enables controlled, change-based promotion from UAT to Production, ensuring only validated updates are transferred.

Overview:

Incremental Migration detects and migrates only the differences between UAT (source) and Production (target) since the last established baseline. Instead of reprocessing entire datasets, it transfers only:

  • New records created in UAT
  • Modified records during testing

This ensures Production receives only what changed and nothing more.

Scenario:

A product team introduces new pricing rules and modifies approval workflows in the UAT environment. During testing:

  • New pricing records are created
  • Existing discount rules are modified

Once testing is complete, the administrator needs to promote only these approved changes to Production without impacting unrelated Production data.

  1. From the Home page, click the up-down arrow () icon next to your username at the bottom of the left panel and click the Go to Administration option.
  2. Expand the Organization and click Migration.
  3. Click Launch Migration Manager.
  4. Select organizations:
    1. The system automatically selects the source organization based on your login.
    2. The system also auto-populates the user ID for the source.
    3. Enter the Client ID and Client Secret for the source organization. For more information on how to generate the client ID and secret, see Configuring an API-to-API Connection.
    4. Select the Target Organization.
      Note:

      Only organizations associated with the same account appear for selection.

    5. Enter the User ID, Client ID, Client Secret for the target organization. For more information on how to generate the client ID and Secret, see Configuring an API-to-API Connection.
  5. Click Validate & Save.

    You only need to validate once for each source-target pair.

  6. Go to the Incremental Migration tile and click select Start Incremental Migration.
  7. Review objects with an existing baseline. Select:
    • Pricing objects
    • Workflow configuration objects
  8. Review the migration details before executing.
  9. Click Start Incremental Migration and monitor progress.
    When all steps are complete and the progress reaches 100%, the system automatically navigates to the Migration Complete page.
  10. Optional: Click Download Report to save a detailed migration report for your records.
  11. Click Return to Dashboard to navigate back to the Migrations dashboard where you can view all migration history.
  • Only UAT-approved changes are migrated to Production.
  • Existing Production data that was not modified remains untouched.
  • Migration completes significantly faster than a Full Migration.
  • The system updates the baseline for future incremental runs.

Production now reflects the validated UAT updates without unnecessary data processing.

Validate pricing rules and workflows in Production.