Two MAPs one CRM. Eloqua and Marketo syncing to SFDC (salesforce)

Highlighted

Two MAPs one CRM. Eloqua and Marketo syncing to SFDC (salesforce)

We currently have two Marketos and one Eloqua instance.  All have their own SFDC instances.  

 

We are batting around the idea of reducing that down to one SFDC and have Marketo & Eloqua both sync with it.  The SFDC instance will be the one attached to the Eloqua instance.  So, new Marketo instance and deprecate the other two.

 

I would love to hear from the community if you have worked in this environment.  We ran this for a brief period two years ago when we migrated from Eloqua to Marketo and really only had an issue with Unsubscribe management.  Eloqua did not play nice.  We can work around this in our new effort.

 

We are going to make these assumptions.  SFDC will be the center of truth.  Eloqua will have records that do not sync to Marketo.  And Marketo will have records that do not sync to Eloqua.  Some records may exist in both.  SFDC will have all of them.

 

We are aware that communication limits will need special management.  

We are going to make sure to reduce duplicate records prior to sync.

We are going to make sure our new Marketo instance is in the same server farm so we can keep our IP addresses and no warming.

We realize CNAMEs will have a default value and one cname will have to be chosen everytime.

 

What are we not considering that you have experienced?  

Do you have any tool recommendations that will help facilitate this?

Do you have any architecture change recommendations?  is a Customer Data Platform a good idea?, etc.