The name of the broker is found in many different files within the workspace, and many of these files could not safely be altered to change the broker name. We know that creating a new workspace will cause an inconvenience for your users but it cannot be avoided. Once their new workspace is established they should have no further problems.
The recommended procedure for them would be to:
1. Before the migration of the SCM Server happens, they should make sure that all their current work is checked in to the Harvest repository.
2. After the migration, they should rename their workspace folder, open Workbench or Eclipse, and create a new workspace connected to the new broker name.
3. Add the needed projects to their new workspace.
4. After this, if needed they can use a folder comparison tool like Winmerge or BeyondCompare to compare the old workspace with the new one to assure that everything is up to date.