Refactor actual service portal

[Consiglia]

Hi all!

with the new release of configurable widgets, we are planning to refactor the service portal we are currently using.

The portal we are using is already the csm.

I'd like to keep the previous, but not reachable to the final users.

What is the best way to do it? I was thinking to create a new portal with csm suffix and change the suffix to the current when we are ready to switch to the new one.

[Satishkumar B]

Hi @Consiglia 

check this:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0716537
https://www.servicenow.com/community/itsm-forum/how-to-get-the-exact-copy-of-a-service-portal-of-ano...

……………………………………………………………………………………………………

Please Mark it helpful 👍and Accept Solution✔️!! If this helps you!!

[Mark Manders · Accepted solution]

That's exactly the way you should do it. In fact: create the new portal on a 'csm_new' suffix and just start creating it. This will enable you to move it to PROD and have a selected audience test it to see if you forgot anything, or anything is not working.

Then you are going to throw a big party on a Tuesday morning with cake and confetti (no champagne, it's still morning!) and you switch the suffix right before that. Make the old one csm_old and the new one 'csm'. And from that moment forward, everyone will end up on the new portal, without having to change favorites or other links in documentation and such.