How do I migrate CCH® ProSystem fx® Engagement or Workpaper Manager Administrator module to a new server?

Prior to starting the Migration Process, please review this important information:

  • The best practice is that the new server be the same CCH® ProSystem fx® Engagement or Workpaper Manager version. If different versions of the Administrator module are installed, the migration may fail depending on the version installed.
    • See step 11 for more details. 
  • Microsoft® SQL Server® versions - The new server will need to have the same version (or greater) of SQL installed that was installed on the original server.
    • Example: If the original server is using SQL 2008 R2 or SQL 2008 R2 Express, then the new server will have to use SQL 2008 R2, SQL 2012, SQL 2014, or (if supported) SQL 2016.
    • Please note that the version of SQL or SQL Express used is dependent on the version of Engagement or Workpaper Manager being migrated. 
  • The following environments are not supported:

To avoid data loss, users should check-in all binders prior to the migration process.

Warning! The steps below only involved migrating the Admin module. If you have other modules on your server such as the Terminal Services Database, all binders from Engagement Terminal Services Client sessions must be checked into the Central File Room (CFR) prior to migration. The Terminal Services Database is not included with the backup of the CFR SQL databases. The Terminal Server Database cannot be migrated.

The following steps must be followed to avoid data loss.

  1. Close all Engagement applications.
  2. On the new server, install the same version of the Engagement or Workpaper Manager Administrator that is on the original server.
  • You can install Engagement 2018 on the new server if you are migrating and updating from Engagement 7.5 or Engagement 2017 at the same time.
  • You can install Engagement 2017 on the new server if you are migrating and updating from Engagement 7.2 or Engagement 7.5 at the same time. See step 9 for further details.
    1. Install and configure a Microsoft® SQL Server® instance for Engagement.
    2. Install Engagement Administrator.
      • Warning! Do not launch the application. 
        • Do not open and configure the Administrator Module on the new server!
        • This will cause the following message on the Workstations once they go to log into Engagement:
          • "The firm for the office server you have specified is different from the firm for the other CCH ProSystem fx Engagement profiles on this computer"
      • If possible, install the program to the same installation path as the path used on the original server. This will simplify the process.
  1. Open the Admin module on the original server.
  2. Locate the CFR(s) in the lower-left corner.
  3. Right-click the CFR and select Properties.
  4. Locate the workpaper path and document it.
  5. Repeat steps 5 and 6 for each CFR.
  6. On the original server, run the Database Backup and Restore Utility and perform a full backup. 
  7. Locate the following services on the Old Server and disable them:
    • PFXSYNPFTService
    • PfxEngDesktop
    • Pfx.Engagement.WcfServices  (v7.0 and later versions only)
    • Pfx.Engagement.SocketService  (v7.2 and later versions only)
      • To disable the services, right-click on the service and select Stop. Then right-click on the service again and select Properties. Change the startup type to 'Disabled' and select Apply. Close out of the Computer Management dialogue.
  8. Copy the .bak file created with the Database Backup and Restore Utility to the New Server.
  9. On the New Server, run the Database Backup and Restore Utility and restore the .bak file that you copied from the Old Server.
    • If the version of Engagement or Workpaper Manager installed on the new server is a 2017 or 2018 release, you will receive a prompt stating there is a database version mismatch. If the backup file is from Engagement 7.2 or 7.5, it should allow you to proceed.
      • Example: Database backup is from Engagement version 7.2 and the installed version of Engagement is 2017.1.1.
      • Note: It is not recommended to restore a back up from an older Engagement version to a newer Engagement version, unless the newer version is Engagement 2017 or 2018.
    • Once the database restore successfully completes, run the Pfx Database Utility to upgrade the databases to the correct version.
      • The Pfx Database Utility is a version specific utility and can be found in the ?:\Pfx Engagement\Admin\Engagement CD Image\Utilities folder, where ? is the drive the program is installed to.
  10. Open the Administrator module on the New Server for the first time.
    • Note: If the server name has been changed, you will be prompted to change the Engagement server name.
      • Select Yes to accept the name change.
  11. Copy the ?:\Pfx Engagement\Admin\Workpapers folder (where ? is the drive the workpapers were stored on) from the Old Server to the New Server's Workpapers folder.
    • If the path is different on the New Server, then you can use the CFR Workpaper utility located in the CD image\utilities folder.
    • The above is the default for the Central File Room workpapers. If the location is empty, the folder may have been moved. You can check the location of the Central File Room workpapers folder by right-clicking on the Central File Room in the Administrator module and choosing Properties
  12. If any of the following folders contain files, copy the content to the corresponding folder on the New Server:
  • ?:\Pfx Engagement\Admin\Admin Packages\
  • ?:\Pfx Engagement\Admin\Archive\
  • ?:\Pfx Engagement\Admin\Transition Binder Packages\
  1. If your Engagement configuration uses one or more secondary office servers, create an admin package on the migrated server and receive it on all other main and secondary office servers.

If the server name changed, each workstation that has Engagement installed will need to do the following:

  1. Have the user log in to Engagement or Workpaper Manager.
  2. A message will display indicating that the program could not find the old server. Select OK
  3. Either select Browse and select the new Office Server, or type in the name of the new Office Server.
  4. Click OK.


  Solution Tools
 Solution Id 000030920/sw17114
 Direct Link
To provide feedback on this solution, please login.

Your feedback about this article will help us make it better. Thank you!