Data Model Migration

The EnterWorks migration feature allows for the transfer of data model elements from one EnterWorks environment to another. The migration feature is designed to facilitate the transfer of initial data model components, plus all future changes and improvements, from DEV to QA, and ultimately to PROD. Each data model component has an underlying unique identifier assigned to it, which ensures the correct migration of components even if their names have been changed.

For example, if we have an attribute called "User Desc" in the DEV environment that is migrated to QA and PROD as "User Desc". Later, the attribute name is changed to "User Description" but all other qualities of the attribute remain the same. A second migration of the profile containing this attribute would successfully locate the "User Desc" attribute in the QA and PROD environments and update its name to be "User Description".

The migration flow should always be from DEV to QA and then to PROD. Development changes and enhancements should always be performed in DEV, migrated to QA, and then migrated to PROD. Conforming to this protocol allows migration to properly locate the data model components to change.