Can store customer entity information in an external database but CRM system still works well?

(0) Share

Report

Posted on by Dung Phung Van

As normal, in Dynamics CRM system, all the information of customers are stored in Customer entity.

But, to adapt my project, we need to store all information of customers in an external database.

Is it possible if whether the CRM system can connect to external database and get customer information if need but don't store it in Customer entity?

Thanks,

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

mscrmba on at

Like (0)

Report

You could store the data in both systems and synchronise the two systems.

Is there a business/security reason you don't want to store the data in CRM (as an Account or Contact)?

Was this reply helpful? Yes No
Dung Phung Van on at

Like (0)

Report

Thank mscrmba!

Firstly, I've been finding out where or not can store the CRM data in an external system?

Secondly, my customer want to store some data in an external system(database) instead of the CRM system.(Maybe coz security and performance)

Was this reply helpful? Yes No
Mahendar Pal 45,095 on at

Like (1)

Report

Hi,

Customer data need to be present in MSCRM, because it is required for other records as well for example associations, reports, dashboards etc. Keeping customer data in another system won't be a good option and require lot's custom development if want to implement workarounds. For example while creating any associated record you can refer record which is present in CRM database using lookup, you can't associate you custom data from other DB to lookup field. So it may be you need to setup some dummy records that you will be setting always default in lookups, it just a simple example there could be different scenarios.

But if you want you can store customer information in both system, or when required can bring in into CRM, we have done this for one of our client where they are using a custom DB to store customer data with additional information.

So better option will be keep custom data in CRM only if want to keep data in other system as well develop synchronization between two systems.

Thanks

Was this reply helpful? Yes No
Verified answer

mscrmba on at

Like (2)

Report

What you could do is have a unique customer ID that is in both CRM and your external system, and maybe a couple of key fields for Account (business/corporate customer) e.g. Account name, primary contact person's name, possibly mobile phone, address and email address.

You may benefit from holding Contact (person) details in CRM.

This would allow you to take advantage of the out-of-the-box Campaign capability of CRM.

You could present the data held in the other system through an iFrame into CRM (or if it's in several systems then USD may provide a unified user experience that works for you).

Or you could essentially keep the information separate, and have minimal synchronisation between the two systems.

Synchronisation could be one way or two ways. Normally CRM is the primary system for customer data for an organisation (so CRM to Other System updates are normally the minimal interface that will be required). But it doesn't have to be that way, and there may be a justification for having the other system as the primary customer data store.

The data you need to store in CRM will really be defined based on what business functions you want CRM to provide / enable for your organisation.

Was this reply helpful? Yes No