HFM/FDM: Steps by Steps Migration

HFM migration steps -

Step0) If the destination HFM app name exists already, delete it first.
Step1) Check source (ex. HFM) and target (ex. PRODHFM) UDL files. They could reside in any HFM servers.

Step2) From HFM server 161, run copy utility

Step3) Ensure the source and destination UDL files are selected correctly

Step4) Select source application, and confirm it will be converted to classic to ensure migration successful. We will need to convert back to EPMA. Click Yes and Yes.

Step5) Select destination.

define the application to copy to and click next

 Copy in process

Step6) After Copy is completed successfully, need to register HFM application, so it can be visible.

Step7) After copy, user Admin is only assigned with provision access. We need assign administration to user Admin. Go to shared service, find Admin, and right click to select provision.

you also can copy provision (select application under consolidation, right select Copy Provision)
Step8) Transfer Classic HFM to EPMA

FDM Migration
Step1) Have DBA migrate the FDM database
Step2) Copy entire folder structure and files from Development, and overwrite to Production

 Step3) Update machine profile in Production server

Step4) Update Application Name and FDM Web Server Name, both under Integration settings

Step5) Update SQL Server properties