Salesforce and Marketo Migration to new instances | Community
Skip to main content
A
Anonymous
July 19, 2018
Question

Salesforce and Marketo Migration to new instances

  • July 19, 2018
  • 2 replies
  • 4073 views

Hello all - I believe this thread belongs here, but please let me know if not, happy to move or have it moved it.

We're undergoing a Salesforce migration to a fresh new org, and we learned we'll need a new instance of Marketo as well. We got the new instance already setup by the Marketo support team (it has a new name but I noticed the Munchkin # it's the same, which is great). I do have a few questions, I searched here on the forum, couldn't find a specific clear answer.

Marketo team asked us to not touch the fresh new instance until we're ready to migrate (which's a process they we'll do), and our timeline for our Salesforce schema and data to go up in Salesforce is tomorrow/early next week. That SFDC instance is not yet hooked up in the new Marketo instance.

  • Is there any harm in starting the Marketo's end migration process right now? (So request the support team to start right away, since they need 2 bdays)
  • Additionally: If there are custom fields that are not going to be ported over to our new Salesforce (from current SFDC), is this ok with the new Marketo instance? (once we connect both new instances) ?
  • From a record/data point of view, I'm thinking SFDC -> Marketo (since I can bulk upload to SFDC directly)?
  • How will our domain be affected? Will we keep the same domain for resources we currently have (Landing Pages, links etc)? Is there any redirect work to be done?
  • Since we're in a new instance, I imagine all Marketo Ids will be new to the new records (I'll be keeping 2 copies of all records, one in Postgres, and one physical backup), and have a column with the Marketo Idls (Old). Will my leads and contacts be ok with their munchkin tracking with the new marketo ids?

Thank you so much for your help, I'm happy to document here any challenges and gotchas along the way for anyone interested

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    Josh_Hill13
    Josh_Hill13
    Level 10
    July 20, 2018

    There are some migration threads you should research here. Most of these questions should be discussed with your Support Manager.

    1. Starting Migration Now - I don't see why not?
      1. You should expect some migration period if you haven't moved over the important programs or lead lifecycle, assets yet. Are they doing some of that?
    2. Old Custom Fields - sure if they do not exist in your new SFDC. Just make sure Support knows what you want migrated.
      1. if your custom fields are referenced in migrated assets, that will cause an error.
    3. Data Load: not sure what you are planning. Generally you want your SFDC clean before a sync. So what exactly is Marketo migrating?
    4. Your cname can be the same in Admin and you'll need Marketo's help to move any assets.
    5. Munchkin Assoc - best to ask support.
    A
    Anonymous
    July 20, 2018

    Thank you Josh, I'm opening a case right now with Marketo Support team to start - so 1

    2. I have an extensive list of all the custom fields we'll keep, so I'll use it with support as well, in case they needed. We removed unused or legacy custom fields as well as packaged ones.

         2.1 good call - I'm thinking "no" but I'll double check.

    3. I'm going to add all our leads/contacts/accounts/campaings etc data using Salesforce dataloader, so it'll be in our new Salesforce before we sync with new Marketo.

    4. Thanks, I'll ask them for that.

    5. Will do.

    Thank you again for your time.

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    July 20, 2018
    • How will our domain be affected? Will we keep the same domain for resources we currently have (Landing Pages, links etc)? Is there any redirect work to be done?

    New account string = different CNAME value ("value" as in rdata / the right-hand-side of the CNAME record).

    Thus you'll want to reduce the TTL on your existing CNAME record as low as possible to allow for quick migration.

    A
    Anonymous
    July 20, 2018

    Hi Sanford, thanks for the help -  ok - I'll follow the advice, I'll check in with some of our internal engineers that happen to be great with this as well, and check back here for our findings.

    Thanks for your help

    Terms & ConditionsAccessibility statement

    Loading footer...