About Entity Migration

Entity migrators are Deployment Management object types. Each migrator is designed to migrate a specific kind of OpenText PPM entity and all of its dependent objects from one OpenText PPM instance to another.

You can use Deployment Management to manage configuration changes to OpenText PPM. Deployment Management comes with a set of preconfigured object types, or entity migrators, that you can use to move OpenText PPM configuration entities (workflows, request types, and so on) between OpenText PPM instances. If you maintain scratch instances for developing and testing OpenText PPM configurations before you deploy them into your production instance, you must use these entity migrators, and develop a workflow that drives configuration changes through your source configuration management deployment process.

Migrating configurations using entity migrators and workflows lets you automate and standardize a change-control process for your OpenText PPM implementation. You can build a workflow for every migrator object type, or create a single generic workflow for all migrator object types.

You can migrate the following OpenText PPM entities:

• Special commands

• Object types

• Portlet definitions

• PPM Dashboard modules

• PPM Dashboard data sources

• Project types

• Work plan templates

• Report types

• Request header types

• Request types

• User data contexts

• Validations

• Workflows

• Workflow step sources

• Overview page sections

• Subworkflows

• Program types

Migration Order

If you plan to migrate request type, workflow, project type, and work plan template configurations that are related to each other, you must perform the migration in the following order:

1. Request type

2. Workflow

3. Request type again (if circular references exist between request type and workflow)

4. Work plan template

5. Project type