Follow these steps to resolve the issue:
1. Contact Symantec Support for a copy of the script to repair the SSIM proxy and restore the synchronization jobs. For more information, see "How to engage Symantec Support for help with Control Compliance Suite" at http://service1.symantec.com/support/intrusiondetectkb.nsf/docid/2007110510041753.
2. Create credential object in destination SQL server with the name “SYMC_E9B379F5-61BE-4e4f-BA1B-3AA37DC91AD2” in Security/Credentials folder with App Server credential.
3. Run CreateProxy.sql on msdb database to create the "SYMC_02C294C2-2193-4e4b-A67A-0A2D27FB871F" proxy object.
4. Run SSISPackageImporter tool to import SSIS packages. Use the following command line:

SSISPackageImporter.exe "<Report server name>" "D:\MigrateDB\GoldSpec\install_reporting_packages_specs.xml" "D:\MigrateDB\GoldDtx"
Note: SSISPackageImporter.exe “help” - will give you the command line argument details

5. Run SQLAgentJobCreator tool to create SQL Agent jobs. Use the following command line:

SQLAgentJobCreator.exe "server=<sql server name>,1433;Initial Catalog=msdb;Trusted_Connection=Yes;" "D:\MigrateDB\GoldSpec\install_reporting_job_specs.xml" "SYMC_02C29
4C2-2193-4e4b-A67A-0A2D27FB871F" "<sql loginname>"

Note: SQLAgentJobCreator.exe “help” - will give you the command line argument details.
6. Test the automatic reporting synchronization jobs for functionality.