Adobe SiteCatalyst Migration Paths with Satellite

In a previous post, I talked about what the steps were to get the Adobe SiteCatalyst base code setup within Satellite TMS.  That post is a great primer for getting started with SiteCatalyst for the first time, but what if you already have an implementation?  What will you have to do to handle a web site that already has an extensive implementation in place?  Today I will walk you through the options that are provided to you by Satellite to help in migrating an existing SiteCatalyst implementation without losing your mind.

Migration does not have to be painful.

When you set out to migrate your SiteCatalyst implementation into a TMS, it can be a scary proposition, but it does not have to be.  With Satellite, you do not have to rip the bandaid off all at once.  With the options that we provide, you can ease into the migration if you choose and take the time you need not only to get the IT resources lined up to help with the migrations, but to make sure you have the time to begin using your brand new TMS right away.  Instant gratification!! The options we will be talking about are all located in the General tab of the SiteCatalyst configuration section.

Screen Shot 2013-02-14 at 8.52.53 PM

What if you cannot remove the existing page code but you want to go ahead and start using Satellite?

This is a one click fix.

Screen Shot 2013-02-14 at 8.28.07 PM

If you select this option, Satellite will not deploy any page code to the site, but you can still go ahead and add rules and expand upon your implementation without having to wait for all of the old code to be removed from the site.  Once the legacy code has been removed, you just uncheck this box and then Satellite will begin to deploy the SiteCatalyst page code to your site, allowing you to get the benefit of the TMS right away without having to wait. Go ahead and get your link tracking on right away, and you can plan a suitable migration plan for the rest later. Create value on day 1 without having to move mountains.

What if  you have an amazing s_code.js file already?

This is a easy fix as well.  Under the scode configuration section, select URL instead of Satellite Managed, and then you will be presented with two fields to provide the URLs for where the secure and non-secure versions of your existing scode files are located (Satellite will automatically handle switching). Satellite will be able to leverage your existing file, and then you can use Satellite to expand your implementation though the rules and additional features that Satellite provides.

Screen Shot 2013-02-14 at 8.38.31 PM

What if you want to leave your existing implementation completely intact?

Satellite provides the means for you to have a completely separate SiteCatalyst implementation while leaving your original one intact, allowing you to run them in parallel.  To do this, you can simply rename the main s object for SiteCatalyst for the new installation.

Screen Shot 2013-02-14 at 8.56.57 PM

Once you rename the SiteCatalyst object then you are able to run both implementations: your original one and the one within the Satellite TMS.

Choose your own path.

Every website and every company is unique and has its own set of hurdles to jump when planning out a migration of SiteCatalyst into a TMS.  It is important to choose a solution that offers you the flexibility you need to be able to handle the migration on your terms and your timeline.

If you would like to hear more about Satellite TMS and the migration options with moving SiteCatalyst inside of Satellite, you can reach me at

Related Posts

Join the Conversation

Check out Kelly Wortham’s Optimization based YouTube channel: Test & Learn Community.

Search Discovery
Education Community

Join Search Discovery’s new education community and keep up with the latest tools, technologies, and trends in analytics.

Follow Us

Scroll to Top