In a pre­vi­ous post, I talked about what the steps were to get the Adobe Site­Cat­a­lyst base code set­up with­in Satel­lite TMS.  That post is a great primer for get­ting start­ed with Site­Cat­a­lyst for the first time, but what if you already have an imple­men­ta­tion?  What will you have to do to han­dle a web site that already has an exten­sive imple­men­ta­tion in place?  Today I will walk you through the options that are pro­vid­ed to you by Satel­lite to help in migrat­ing an exist­ing Site­Cat­a­lyst imple­men­ta­tion with­out los­ing your mind.

Migration does not have to be painful.

When you set out to migrate your Site­Cat­a­lyst imple­men­ta­tion into a TMS, it can be a scary propo­si­tion, but it does not have to be.  With Satel­lite, you do not have to rip the bandaid off all at once.  With the options that we pro­vide, you can ease into the migra­tion if you choose and take the time you need not only to get the IT resources lined up to help with the migra­tions, but to make sure you have the time to begin using your brand new TMS right away.  Instant grat­i­fi­ca­tion!! The options we will be talk­ing about are all locat­ed in the Gen­er­al tab of the Site­Cat­a­lyst con­fig­u­ra­tion sec­tion.

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, Satel­lite will not deploy any page code to the site, but you can still go ahead and add rules and expand upon your imple­men­ta­tion with­out hav­ing to wait for all of the old code to be removed from the site.  Once the lega­cy code has been removed, you just uncheck this box and then Satel­lite will begin to deploy the Site­Cat­a­lyst page code to your site, allow­ing you to get the ben­e­fit of the TMS right away with­out hav­ing to wait. Go ahead and get your link track­ing on right away, and you can plan a suit­able migra­tion plan for the rest lat­er. Cre­ate val­ue on day 1 with­out hav­ing to move moun­tains.

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

This is a easy fix as well.  Under the scode con­fig­u­ra­tion sec­tion, select URL instead of Satel­lite Man­aged, and then you will be pre­sent­ed with two fields to pro­vide the URLs for where the secure and non-secure ver­sions of your exist­ing scode files are locat­ed (Satel­lite will auto­mat­i­cal­ly han­dle switch­ing). Satel­lite will be able to lever­age your exist­ing file, and then you can use Satel­lite to expand your imple­men­ta­tion though the rules and addi­tion­al fea­tures that Satel­lite pro­vides.

Screen Shot 2013-02-14 at 8.38.31 PM

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

Satel­lite pro­vides the means for you to have a com­plete­ly sep­a­rate Site­Cat­a­lyst imple­men­ta­tion while leav­ing your orig­i­nal one intact, allow­ing you to run them in par­al­lel.  To do this, you can sim­ply rename the main s object for Site­Cat­a­lyst for the new instal­la­tion.

Screen Shot 2013-02-14 at 8.56.57 PM

Once you rename the Site­Cat­a­lyst object then you are able to run both imple­men­ta­tions: your orig­i­nal one and the one with­in the Satel­lite TMS.

Choose your own path.

Every web­site and every com­pa­ny is unique and has its own set of hur­dles to jump when plan­ning out a migra­tion of Site­Cat­a­lyst into a TMS.  It is impor­tant to choose a solu­tion that offers you the flex­i­bil­i­ty you need to be able to han­dle the migra­tion on your terms and your time­line.

If you would like to hear more about Satel­lite TMS and the migra­tion options with mov­ing Site­Cat­a­lyst inside of Satel­lite, you can reach me at