Bring in fields from my SFDC to a new marketo instance - if an existing marketo is already connected to that SFDC?

JProst

I am currently setting up a brand new Marketo instance to replace my live one... for back end issue purposes. The new instance will be exactly the same as the live one.

We need to bring all the SFDC fields into the new Marketo so we can rebuild all the programs etc. I think the best way to do this is to connect the second instance to the same SFDC and let it sync, then turn off the sync. Note: We are not trying to connect one marketo to two SFDC instances.

Although Marketo doesn't recommend connecting two Marketo instances to the same SFDC, I have read that it is possible and OK if the following is true:

1. Use a different SFDC user to integrate. You can't sync using the same SFDC user.

2. Disable the instance after it has synced. No reason to leave them both on.

3. We don't have MSI

4. We won't be pushing ANY new data into SFDC with the new Instance, so we won't have an endless data update problem. And when we do, we can make sure it doesn't get pulled back into Marketo by using the "Exclude from Marketo" field that's connected to our custom sync rule.

Am I missing anything? Has anyone else had this challenge, and how did you do it?

JP

SanfordWhiteman

1. Use a different SFDC user to integrate. You can't sync using the same SFDC user.

Let’s say you’ll be infinitely safer if you have a different SFDC User (i.e. different profile and permission set).

2. Disable the instance after it has synced. No reason to leave them both on.

You don’t need to disable, but in your case, sure. Again the less surface area to create endless updates, the better.

4. We won't be pushing ANY new data into SFDC with the new Instance, so we won't have an endless data update problem. And when we do, we can make sure it doesn't get pulled back into Marketo by using the "Exclude from Marketo" field that's connected to our custom sync rule.

Well, the Do Sync/Do Not Sync boolean can’t account for all cases.

I would ensure your SFDC User used for the sync can only access a small set of test people (via sharing rules).