Hi Barbara!
If you're wanting a biased opinion on best practices... I'm happy to contribute here.
If the customer is 100% certain that they do not have any use for an integrated CRM (regardless of whether they want to keep it for historical purposes or not), it's a best practice from an integration standpoint to remove the impacts that the Sage CRM integration has on the Sage 100 system. This ensures data cleanliness, but also removes any potential data points in Sage 100 records from coming up and creating problems for the customer down the road.
From a high-level step-by-step standpoint, here's what you'd have to do:
- Run a script within SQL to remove references of Sage 100 data across impacted Sage CRM tables (setting all values to 'null' values) - I may have a canned script that I use that I can share the script.
- (optional) Validate within Sage CRM that the links are gone.
- Within Sage 100 while all users are out of the system (typically an after-hours task) - run the "Rebuild CRM" utility.
- This utility is the equivalent of saying "all Sage 100 references to Sage CRM are wrong. Use what's in Sage CRM." Since all references in Sage CRM are blank at this point, it forces a break/removal of any linkage between Sage 100 and Sage CRM.
- This utility can take several hours to complete if there are many records of Sage 100 that were integrated/linked to Sage CRM.
- Within the same utility menu, run the "Purge Quote/Order Data"
- This does exactly as advertised.
Once that's all done, disable the Sage 100 integration engine service (and any service that might be installed as a part of the upgrade).
At that point, you're 100% free to do whatever you need within Sage 100 free and clear of Sage CRM's status or integration. I hope that helps!
------------------------------
Best Regards,
Basil Malik
e: bmalik@netatwork.com
------------------------------