Marketo to AWS data center Migration Questions

Our clients are all on the Amsterdam pod, and we didn’t do anything beforehand. We just let it happen. Yes, probably not the perfect preparation, but on the other hand: Anything else would have been way too much effort.

Adobe says in its docs that the migration happened, so I guess we have to believe it did.

So what’s the situation now? Well, we don’t really know. We have issues we never had before. GoToWebinar authentication doesn’t work anymore, at least not the way it used to. We have an open ticket on the Marketo/AEP integration, and many users report UI slowness and various UI errors.

Webhooks seem to be fine, Launchpoints are unaffected it seems.

So you see, my answer is inconclusive. I can’t say for sure that the migration happened, and I can’t say that what we’re seeing can be blamed on the migration. Sorry :-).

I did no prep for this migration. Marketo automatically paused everything and it started again afterwards...but it also happened during off hours for us. I didn’t even have any sync errors from our custom integrations (which caused me to reach out to Marketo Support to confirm it even happened). There was no impact on the business except that we delayed sending a single email from Friday afternoon to Monday morning because it was close to the migration window.

We had ours back on July 17th! We use embedded forms, and we were also lucky with a Friday migration window. Here below is a a short list of items to consider though they may not all apply to your situation.

To your questions:

• I unfortunately have no screenshots of what the forms looked like during the window. However, I can confirm all form fill data was captured and processed post-migration. 
• The migration did complete within the window assigned with zero delays. No campaign backlogs in marketo and no sync backlogs with SFDC after migration.
• We opted to make zero changes to our integrations since we worked hard to mitigate impact otherwise. 

Hope some of the above and the below can help!

--

• Identify cross-functional stakeholders who could be affected by the downtime and help mitigate impact
  • Tip: Give stakeholders ample notice, send biweekly reminders, hold focused check-in calls the week before, and offer office hours during migration week in case any issues require escalation or support.
• Align with Salesforce admins to ensure no refreshes, bulk loads, or bulk changes occur during the migration window.
• Ensure Sales Managers and Sales Operations understand there will be a brief window where lead hand off and routing slows down and help reassure Sales Reps that their leads will arrive, just with a slight delay!
• Create and share a tracker of embedded forms, so everyone works from the same list.
• Share embedded form IDs with Marketo Support at least a week before the migration window so form fills during the migration can be collected and processed afterward.
• Freeze new form development the week leading up to and a few days after the migration window to ensure no form data is left behind!
• Align with Demand and Marketing Managers to ensure no major campaign launches occur on migration day or in the one to two days beforehand if those campaigns drive traffic to embedded Marketo forms.
• Align with Digital Media Managers to ensure paid media campaigns directing traffic to embedded Marketo forms instead point to other valuable, persona-aligned marketing assets.