SOLVED

Re: Microsoft Dynamics - Marketo Intergation Upgrade

Go to solution

Microsoft Dynamics - Marketo Intergation Upgrade

Hi!

We are in the process of CRM migration from Microsoft Dynamics on-prem to cloud/365. This means that we also have to connect Marketo to the new CRM, and as I've checked so far - and we've been told the same also by Marketo support - the only way to do that is to get the new Marketo instance. Unfortunately, this is not a small task to do, we might have to forget some data and it also requires significant engagement on our side. Understandably, we want to avoid that scenario if possible.

Therefore I'd appreciate some advice on alternative options in case there are any. The one I found is to simply pause the current integration to Dynamics and instead introduce a 3rd party integrator (such as Informatica, Bedrock Data, Zapier - am I missing any?) and use it to connect to the new CRM. Are there any other/better ways to approach that?

Thank you in advance!

Best;matjaž

1 ACCEPTED SOLUTION

Accepted Solutions
Josh_Hill13
Level 10 - Champion Alumni

Re: Microsoft Dynamics - Marketo Intergation Upgrade

You would have to build your own sync processor, which may or may not create lots of issues. Then you have to support it.

When you have to switch instances, Support can help you load the data and in some cases, move some amount of the logs. I have heard that they do not typically move the logs, so you would lose the behavior history. In all honesty, do you need that? Scoring is near real time or real time. You might need things like bounce history, but those people should get flagged as Invalid or Suspended anyway.

My point is the risk to data loss is limited and may be irrelevant to your business going forward. The cost of running a separate API based sync, which will cost alot of money to build, maintain and then cost API calls, which will also cost money.

View solution in original post

5 REPLIES 5
Josh_Hill13
Level 10 - Champion Alumni

Re: Microsoft Dynamics - Marketo Intergation Upgrade

You would have to build your own sync processor, which may or may not create lots of issues. Then you have to support it.

When you have to switch instances, Support can help you load the data and in some cases, move some amount of the logs. I have heard that they do not typically move the logs, so you would lose the behavior history. In all honesty, do you need that? Scoring is near real time or real time. You might need things like bounce history, but those people should get flagged as Invalid or Suspended anyway.

My point is the risk to data loss is limited and may be irrelevant to your business going forward. The cost of running a separate API based sync, which will cost alot of money to build, maintain and then cost API calls, which will also cost money.

Josh_Hill13
Level 10 - Champion Alumni

Re: Microsoft Dynamics - Marketo Intergation Upgrade

You can also export the data logs to an MDW, then do a bulk API import later using talend or something.

Re: Microsoft Dynamics - Marketo Intergation Upgrade

Thank you for your insight. These are all very valid points, and yes, at the end of the day we'll try to make the best decision from the business point of view.

Definitely, I'll investigate a bit more with the Support what can be done, because, as you've said, any integration comes with an additional price-tag (and also requires some additional work as well). As this is the first time we'll do the upgrade, I'd just like to make sure we have all the options on the table and don't overlook some nifty trick that's maybe out there (I know chances are small, but still ).

Michael_Larmon
Level 1

Re: Microsoft Dynamics - Marketo Intergation Upgrade

Our organization is also upgrading our Dynamics CRM which we were told would involve spinning up a new instance.  We just renewed our contract with Marketo, is there a cost involved with spinning up a new instance and cloning our data?

Thanks

Grégoire_Miche2
Level 10

Re: Microsoft Dynamics - Marketo Intergation Upgrade

HI Michael,

always better to open a new thread than reopening an old one. You will get more answers, quicker

Call support for this, BTW.

-Greg