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 the hardware and software requirements based on relevant documents such as the System Compatibility Matrix, or by consulting Micro Focus SaaS for sizing information.

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

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.

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

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

Micro Focus SaaS provides trainings to customer resources that will support the migration process.

• 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 and Micro Focus 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.

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.

The initial migration run includes the following tasks:

1. Work with PS, Micro Focus SaaS 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.

You should send the following notifications:

• Notify PPM users of the production downtime before the scheduled migration.
• Notify Micro Focus SaaS and PPM users when the migration is completed.

Micro Focus SaaS 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 Micro Focus SaaS services if the on-premises migration fails.

You should send the following notifications:

• Notify PPM users of the new access information.
• Provide PPM users with tier 1 level support information.

Micro Focus SaaS sends the following notifications:

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

Micro Focus SaaS 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 Micro Focus SaaS network.