An alternative to the Sage 200 classic integration is Qmulus Qnect which is developed by our Business Partner Qmulus. The support boundaries for this software can be seen below. TIP: For further information on Qnect software, please see www.qmulus-solutions.com Query | Who Supports This? | Description | Installation & Configuration of Sage 200 API using Native API* | Sage | Set up of the Sage 200 API with Native API for use with the Qnect Connector - guide can be found here | Installation & Configuration of Qnect Connector**/*** | Qmulus | Initial installation of the Qnect Connector | Data Migration** | Qmulus | Migration of either classic or integrated data to Qmulus Qnect Connector | 'How to' queries | Sage | Assistant with core Sage CRM functionality | Technical support for Qnect | Qmulus | Troubleshooting issues via web, phone or remote support | Data Investigations | Sage | Investigation of issues within the Sage 200 or Sage CRM database | Qnect Connector Software Updates | Qmulus | Updates provided to fix issues or improve functionality | Qnect Connector Bug Fixes | Qmulus | Fixes to reported issues via hotfix or software updates |
* Setting up the Sage 200 API is the responsibility of the customers' Business Partner. Any support queries or issues must be raised to Sage, not Qmulus. Further information on API responsibility can be found here. ** The installation and configuration of the Qnect connector, as well as the migration of CRM data from SMS Connected/200 Integrated to Qnect Connector should be undertaken by a CRM Accredited Business Partner. For support, documentation or training on this please speak to Qmulus. *** Compatibility information for the Qnect connector can be found here. NOTE: Guidance on circumstances where a customer get support across mutliple business partners can be found here |