Sage 100

Upgrade planning question for customer with integrated Sage CRM and Sage 100, now that the CRM files are in System, not individual companies. You do a test upgrade to new Sage 100 and CRM installs. When it is time for the live upgrade, you don't really want to remigrate all the system files. Can you just move the CU_ files? For CRM, what do you need to move? Backup and restore the database and fire up the database upgrade script? @SageCRM

Hi @BazMalik! Can you offer an opinion?

@PhilMcIntosh : I have not done upgrades to Sage 100 systems integrated with Sage CRM personally (I've only had to handle the Sage CRM part) ... so that's my asterisk to what follows... From what I know about the process, you could in theory do the same things with the CU_ files that you do with any of the other table files. **However** : There's a glaring possibility that the mirrored tables will be missing data, and you're going to spend time chasing missing links. Going the route of just pulling the files over, you'll have to run the Rebuild CRM utility to ensure you populate the Sage 100 mirrored tables as best as you possibly can. That all said - I wouldn't necessarily go the route you're describing as it's not the norm, but you _**can**_ do it so long as you know there's some additional steps required.... steps that might end up taking just as long to do compared to just doing the upgrade on the live environment using the installers.

@BazMalik - so on the CRM side make sure any tweaks are documented so they can be replayed after doing the CRM install/upgrade process again? If that is the case then shouldn't the CU_ files be in sync if copied from old to new Sage 100?

Well really any new customer records, Sales Orders/Opportunities, Contacts, and Ship To Addresses are all potential items that may need to have the links re-established. So I would document those. The CU file structure will be in sync, but the information contained within them may have discrepancies. My assumption in the response above was that you would be creating a test environment running in parallel to a live environment. As such, if you upgrade the test environment, it's not capture the addition of records to the CU tables that have been made in the live environment. Hence the necessity to run the Rebuild CRM utility to ensure that the mirrored tables are populated with the most up to date information and all records that may have been created in one system or the other and synchronized are linked and synced correctly. My concern isn't more based around the file structure itself, but rather the integrity of the synchronization itself as that is the biggest hassle of the native Sage integration between 100 and CRM.