Working in multiple IDMC organizations

Learn how to design integrations in test, migrate assets to production, and manage edits across Informatica Data Management Cloud (IDMC's) two organizations.

Working in multiple organizations

The UW-Madison Informatica Data Management Cloud (IDMC) instance has two "orgs": test (for designing and adjusting integrations) and production (hosting polished integrations). Maintaining this distinction is a responsibility for all IDMC integrators, and the following information will help uphold best practices and foster a collaborative environment.

Building integrations in test

Integrations should always be designed and tested within the test environment, and adjustments to existing production integrations should also be tested in the test environment. This serves several purposes, including:

  • Allowing integrators to gain familiarity with new-to-them IDMC functionality.
  • Making sure changes won't break a production integration.
  • Testing efficiency with larger data loads without affecting other integrations in the production environment.
  • Maintaining a backup of existing production processes and integrations in case of an outage.

Once an integration's functionality has been confirmed, it can be moved to production.

Asset migration

When moving IDMC assets from test to production, there are several methods available, each described below.

Import and export

IDMC has built-in functionality for the export and import of assets between organizations. This is a user-friendly, no-code approach through the IDMC user interface.

IDMC assets tool

The DoIT Integration Team has utilized fuctionality within Informatica to synchronize assets between test and production, located at this repository. Please contact the DoIT Integration Team at integration-platform@doit.wisc.edu if you would like access.

Editing production integrations

Once an integration has been moved to production, that does not mean it is permanent. Maintenance, unforeseen bugs, and new requirements may all require an integration and its assets to be adjusted after deployment.

All edits should be made within the test environment before being applied to production — either through the export and import process or by manually editing the assets to match. 


Keywords:
test environment, production environment, asset migration, IDMC, export and import, IICS assets tool, integration deployment, DoIT Integration Team, environment management, integration maintenance, best practices, org structure  
Doc ID:
159954
Owned by:
Charles C. in Integration Platform
Created:
2026-03-16
Updated:
2026-04-15
Sites:
Integration Platform