Merging and migrating primary site domain | Community
Skip to main content
June 29, 2015
Solved

Merging and migrating primary site domain

  • June 29, 2015
  • 2 replies
  • 5008 views

We are modernizing and consolidating several websites across different domains. Our primary site will change as well (oldsite.org to newsite.com). What is the best approach for transitioning our existing Marketo forms and pages to the new site? I'm sure we will need to change our CNAME setup, but how do we go about doing that most efficiently and safely on a live instance?

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

I assume you've read Manage Multiple Domains and Microsites, right?

You don't necessarily have to worry about changing your "canonical" domain immediately because you can set up your new domain as a Domain Alias for testing purposes.  Get that CNAME pointed to Marketo and run some tests. 

The difficulty of a full changeover is going to depend on how many places you hard-coded the old domain: for example, if there are links on your LPs that point explicitly to //pages.oldexample.com/unsubscribe.html, that's going to be more annoying than if they pointed simply to /unsubscribe.html (or, if offsite, if they pointed to a variable like {$landingpagedomain}/unsubscribe.html instead of spelling out the domain). 

There's no way to completely avoid people landing on the old domain by clicking links in old emails, so you would also set up a Redirect Rule for the old domain when you go live with the new one. But you want to minimize such redirects because they look clumsy and add network overhead.

2 replies

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
July 1, 2015

I assume you've read Manage Multiple Domains and Microsites, right?

You don't necessarily have to worry about changing your "canonical" domain immediately because you can set up your new domain as a Domain Alias for testing purposes.  Get that CNAME pointed to Marketo and run some tests. 

The difficulty of a full changeover is going to depend on how many places you hard-coded the old domain: for example, if there are links on your LPs that point explicitly to //pages.oldexample.com/unsubscribe.html, that's going to be more annoying than if they pointed simply to /unsubscribe.html (or, if offsite, if they pointed to a variable like {$landingpagedomain}/unsubscribe.html instead of spelling out the domain). 

There's no way to completely avoid people landing on the old domain by clicking links in old emails, so you would also set up a Redirect Rule for the old domain when you go live with the new one. But you want to minimize such redirects because they look clumsy and add network overhead.

July 7, 2015

Thanks Sanford. The domain alias worked; anything I type in with .org now also loads when I change it to .com, which alleviates the concern about what happens when the new site goes up and all .org pages 301 to the new .com pages. The question remains then how do we transition creation of new pages so they use .com instead of .org by default. Is it as simple as updating the Domain Name section of Landing Pages within Admin? Will changing that break anything?

Courtney_McAra4
New Participant
August 7, 2015

+Subscribing...

Gordon McCallum​ - Same question here and curious if you finally pulled the trigger.  We are transitioning to a new domain.  We've set up up the redirect rule and it works.  But when creating new landing pages the default is to use the OLD cname in the URL, and of course we'd like to use the new one, and not ahve to remember or manually change it.  I'm just tentative to make that change in Admin......  Did you do it? 

June 30, 2015

Moved your post to Products and Support