Sage 300 CRE®

This page details how to manage hh2 while upgrading Sage 300 CRE or migrating to a new server.

1. Notify Users: Inform all Sage and Procore users that data will not sync during the upgrade. Note that failed items can be retried once the upgrade is complete.

2. Disable Service: When ready to begin, stop and disable the hh2 Synchronization Service on the server.

3. Perform Upgrade: Complete the Sage upgrade according to Sage’s instructions. Upgrade data if necessary and test all modules to ensure success.

4. Restart & Test: Set the hh2 Synchronization Service back to Automatic and start the service.

   • Open Sage Job Cost to ensure it has no errors.

   • Optional: Test a commitment or two to verify the connection.

1. Notify Users: Inform all Sage and Procore users that data will not sync during the migration. Failed items can be retried after the move.

2. Document Settings: Open the hh2 Synchronization Client UI on the current server.

   • Take screenshots of the Local Connection and Cloud Connection tabs for reference.

3. Uninstall Old Client: Just before starting your database backup, uninstall the hh2 Synchronization Client from the old server.

   Important!

   Do not simply disable the service; the client must be uninstalled to ensure it does not attempt to run during or after the migration.

4. Perform Migration: Complete the migration according to Sage’s instructions. Upgrade data and test all modules on the new server.

5. Install New Client:

   • Download the hh2 Sync Client on the new server from https://synchronization.hh2.com.

   • Log in to Sage as a security administrator to ensure the Sync Client has proper ODBC access.

   • Test Sage Job Cost and (ideally) one or two commitments to verify the connection.

6. Final Cleanup: If you only disabled the sync client on the old server previously, you must go back and uninstall it now to prevent data conflicts.