First time cloning - Dev to Prod?

[Tim_Berger]

Would like to get some input from someone that has dealt with this already.

Question: What is the preferred method - best practice - recommended when moving your content from the Development instance to the Production instance?

Background: The Dev instance still has all the content from SN in it from when SN originally stood it up (Example flows and users)...

Nothing has been moved into the Prod instance at this point. We are hearing mixed messages on what is best to do. 1st we were told to move things into the Prod instance thru update sets. Then we were told it is easier to Clone the existing Dev to Prod then run clean up scripts afterwards, and if anything is broken SN will revert our Prod instance back. Then we would just clone it again and do a manual clean up in our Prod instance.

'From experience, what is the preferred method?

[Deepak Ingale1]

I liked the second method you suggested Jeremy.

Directly start working on PROD from day 1 and if everything is fine, then clone PROD to DEV.

Has any1 used this approach before and are there any issues using this method those my small brain cant imagine?

[Uncle Rob]

If you've got the benefit of being on Day 1 do your due diligence and migrate chunks of code via update sets as you finish and test them.

Do you know how many SN implementations go from start to finish with no changes to requirements, and no bad code, and no redeveloped features?   NONE.     An entire implementation in one instance without proper code migration is both risky and justifies terrible habits.

Also, depending on your industry, its a good way to get your company audited into oblivion.

Do it the hard way.   Update sets + promotion process.

[Deepak Ingale1]

Hello Rfedoruk,

Appreciate your reply and suggestions

We have only two instances, one is DEV and other is PROD. Don't ask me why it is like this and you might be knowing the answer for it.

So will it be a good way to start directly on PROD because even if we start in DEV, we will be performing UAT over there only.

[Uncle Rob]

Hey Deepak,

SN now only packages two instances per purchase (in the old days you'd get Dev, Test, and Prod).   A sales rep can give you the best info on getting new instances, but last time I did so it was $14,500 USD annually.  

Even in a two instance environment, I would strive to keep Prod pristine.   I'd just get way more disciplined about development sprints so I can fit in clone-downs.   I decide on a fixed number of things to develop in an interval, then have users test those things immediately after development.   If the code passes usage, that update set gets sent to Prod.

Having recently worked in the Pharma space, I learned first hand the terrible financial and cultural consequences of lax promotion control.   I tend to be more OCD about it than my peers.

[Deepak Ingale1]

Thank you again and appreciate your suggestions