Zboot and reimplementation process

[SAS2]

Hi, we currently have 3 instances, dev, qa and prod and are in the process of zbooting the qa instance and reimplementing SN. I'd like to get some ideas for the go live strategy. Do we request/purchase a new instance to be the future prod, move update sets from zbooted QA to the new presumably prod?  

Can you please share some ideas or thoughts on the best approach for this.

Thank you,

S.

[Maik Skoddow]

Hi

sorry, but it is really confusing what you wrote. It is not clear how the different questions are related to each other. 

Please provide more details and explain better WHY you have zbooted your QA.

Maik

[SAS2]

Hi Maik,  We have a very heavily customized instance that existed way before even the Aspen release and it was decided to revert back to out of box for all the obvious reasons through a zboot.  The instance we zbooted is the QA.  While we are reimplementing, the end users will continue to use current prod until the cutover period begins. 

I am looking for the best approach for go live.

Once thought comes to mind is to purchase a new prod instance and use it as the go live instance. Promote all update sets from the zbooted instance and deploy in the new prod instance following the standard methodology.

Looking for other ideas or expert advise. 

I hope my question is clearer now. 

Thanks

S.

[Anil Lande]

Hi,

Owning another production instance will definitely help you to onboard different applications one by one smoothly. But it will add additional cost to your customer.

Owning another production instance will confuse users if all modules are not implemented in one go. It would be like one application is on old Instance and another is on new instance. 

It is really difficult to suggest best approach as you have been using this instance since long time and many heavily customized. But owning another instance is the only way to go ahead and at least it will allow all users to use all applications to run business.

Thanks,

Anil Lande