Migrate PPM to on-premises

This section provides instructions on how to migrate PPM from SaaS to on-premises. It's relevant only when you are planning to run PPM on-premises.

Note: Activities marked with * indicate that customer resources are required. You should make sure that the resources are available for the activity.

Determine migration prerequisites

Determining migration prerequisites is an important initial step to successfully migrate a PPM SaaS production instance to on-premises. The prerequisites vary from customer to customer depending on the implementation and other infrastructure requirements.

The following is a typical list of prerequisites that should be considered:

Area Details
Determine the scope of PS engagement

Determine the scope of professional services (PS) engagement required to perform the preparatory and migration activities. The following should be considered:

  • The number of custom objects that need additional configuration and verification.

    This requires capturing all configuration information, customizations, automation built to support the implementation.

  • The number and type of integrations that need to be configured when the implementation is migrated to on-premises, including:

    • PPM-supplied integrations.Document Management, SiteMinder, LDAP Version 3 compliant systems such as LDAP and Active Directory.
    • Custom integrations. Remedy, Peregrine, Crystal Reports, Business Objects, Data Warehouses, ERP systems, and on-premises systems.

  • The number of instances that need to be enabled and copied during and after the migration. These instances include Development, Test, QA, Demo, Training, and Production instances.

  • The infrastructure configurations that require PPM consultant’s expert knowledge of implementing PPM on-premises.
Determine hardware and software requirements

Determine the hardware and software requirements based on relevant documents such as the System Compatibility Matrix, or by consulting the SaaS team for sizing information.

This should include any network configuration information that may be required, such as firewall configurations and so on.

Determine training needs Determine the training needs required for PPM administrators to perform application administration tasks.
Determine system administrator and DBA requirements

Determine the system administrator and DBA requirements for:

  • The entire migration process, including going live on production.
  • The required on-going support of the application and support infrastructure.

Back to top

Schedule migration activities

Migration activities should be scheduled in a project plan. If not, a check list of activities with owners assigned to each activity should be addressed.

The following is an example of the migration project plan.

Activity (*Customer resource required) Details
Project kick-off meeting with stakeholders

Have a project kick-off meeting with the following project stakeholders:

  • Customer representatives. PPM project manager or sponsor, designated PPM administrator.
  • SaaS representatives: Customer success manager and SaaS operations PPM lead.
  • OpenText representatives: Customer sales representative, Customer Support (CS) representative, and assigned PS representative (if applicable).
*Trainings for customers

The SaaS team provides trainings to customer resources that will support the migration process.

*Acquisition of required hardware and software You should make sure that all the required hardware and software are in place.
*Pre-validation activities Work with Professional Services (PS) to determine the pre-validation activities.

Back to top

Perform pre-migration activities

The next phase is to perform pre-migration activities as described below:

Activity (*Customer resource required) Details
*Validation activities

  • Work with PS to perform the pre-migration validation activities, including:

    • Document the current SaaS configuration, customizations, and implementations.
    • List the steps to follow during the migration.
    • Prepare required test plans and procedures for post migration testing.

  • Have a validation checkpoint meeting with PS to:

    • Validate all acquired software and hardware for migration, including versions, sizing, and so on.
    • Verify requisite firewall and other infrastructure configurations are requested and opened for integrations.
*Customer Setup

You should set up the following:

  1. Install the required hardware and software.
  2. Obtain the required PPM license keys.
  3. If required, install vanilla PPM versions on all relevant instances.
  4. If required, integrate with internal systems such as LDAP, SiteMinder, or Document Management.
  5. Configure the firewall and perform other required infrastructure configurations for integrations.
  6. Perform vanilla software validation tests. If required, log service requests with customer services.
*Initial migration run

The initial migration run includes the following tasks:

  1. Work with PS, the SaaS team to perform an initial migration by importing your production PPM file system and database to on-premises development instance.

  2. Work with PS to perform a thorough validation by testing all configurations, process flows, integrations, and customizations (if applicable).

  3. Work with PS to document all issues and resolutions. Make necessary adjustments to the migration activity list.

Back to top

Perform migration activities

Production migration activities are described as follows:

Migration notifications

The following notifications should be sent before and during the migration:

*Notifications sent by customer

You should send the following notifications:

  • Notify PPM users of the production downtime before the scheduled migration.
  • Notify the SaaS team and PPM users when the migration is completed.
Notifications sent by SaaS team

The SaaS team sends the following notifications:

  • Notify the customer before and after the SaaS production shutdown.
  • Notify the customer when the production PPM file system and database archives are available on the FTP site and provide access information for the file download.
  • Notify customer services when the migration starts.
  • Notify the customer to restart SaaS services if the on-premises migration fails.

Production migration run

The production migration run includes the following tasks:

  1. *Work with PS and the SaaS team to perform the production migration by importing your production PPM file system and database to on-premises production instance.

    1. The SaaS team notifies customer of the production service shutdown and creates the file system and database export archives. If required, the SaaS team prepares additional archives for Document Management.
    2. The SaaS team prepares the production archives on an FTP site for you to download.
    3. Work with PS to download the archives and create the on-premises production instance.
    4. PS troubleshoots issues by logging production down tickets with customer services.
  2. *Work with PS to perform requisite validation by testing the configurations, process flows, integrations, and customizations. The SaaS team will assist where needed.
  3. *Copy DEV and TEST instances from the production instances.

Back to top

Perform post-migration activities

Post-migration activities include the following:

Notifications

The following notifications should be sent after the migration:

*Notifications sent by customer

You should send the following notifications:

  • Notify PPM users of the new access information.
  • Provide PPM users with tier 1 level support information.
Notifications sent by SaaS team

The SaaS team sends the following notifications:

  • Notify the customer of the service termination when the on-premises migration is completed.
  • Notify the customer to restart the SaaS managed services if the on-premises migration fails.

SaaS service termination activities

The following SaaS service termination activities should be performed after the on-premises migration:

If the on-premises migration succeeds

The SaaS team will do the following if the on-premises migration is successful:

  1. Notify customer of the service termination.
  2. Shut down all remaining instances and back up the DEV, TEST, and PROD instances. These instances will be stored for 30 days.
  3. Update firewall configuration to block all customer access to SaaS network.
If the on-premises migration fails The SaaS team restarts the production instance and notifies customer when the production instance on SaaS is available.
Summary notification In either case, the SaaS team sends a summary notification to conclude the on-premises migration activities status.

Back to top