Why Integrating Microsoft Dynamics CRM with NAV and Other ERP Systems Is Becoming Ever-More Realistic, and Desirable

Implementing Microsoft Dynamics CRM so that it integrates functionally and technically with the rest of your operations is not as simple as putting the software CD in the tray and clicking "Next". The functional role of your CRM applications should support your organization's business processes (e.g. sales, marketing, service or administration) instead of taking them over or even changing them.

The technical focus is on integrating the implementation in the current infrastructure, so the front end and back end work smoothly together. The challenge lies in smoothly integrating Dynamics CRM with the heart of your organization--the money-making side and the back-office systems.

The Microsoft Dynamics CRM obviously ends its functionality at the invoice. How do you connect it to your ERP system? Personally, I think this is the most interesting part of a CRM implementation, partly because of the risks it entails.

In the Microsoft Dynamics stack, we have three pirmary flavors for ERP: GP, AX and NAV. The last is the most popular in Europe (GP in USA and AX for global players). An interesting development is the launch of Dynamics Entrepreneur (based on Dynamics NAV) and the growth of this product (NAV) in the U.S.

Microsoft's strategy is not to build connections between those systems, but rather to ask other companies to develop the connections for customers

The integrations have improved with the introduction of Microsoft Workflow Foundation in the latest release of Dynamics CRM 4.0 (e.g. Titan release). The solutions from outside vendors like Scribe and Celenia provide the opportunity to easily integrate your back-office system, in this case NAV, with your Microsoft Dynamics CRM application. When you ...