My question is similar as following question, Publish State But I am getting 2013 Prod and restore and upgrade. If I want to DB refresh before GO live from 2013 Prod, My Publishing State will be over written. Without republishing do we have any other alternatives? We have a long gap between UAT and Go-Live, Its very difficult to do content port the large no of items.

Please suggest.

Thanks, Prasanna

  • we already have an accepted answer to the other question (with alternatives as well). In Short, publish states are part of the content manager database. Can you explain how your question is different from the other one? Maybe add how you are publishing (TPM or legacy), if you are republishing your content or remediation of it with with publish states. Suggest that you add a detailed approach and we can add alternatives. Cheers.
    – Shiva
    Apr 2, 2019 at 17:09
  • We are using TPM, In other question they are trying to map different environments where TCM IDS will be different and Topology is different, in My case I am just going to remap my Topology so only missing part is Publishing Status Apr 2, 2019 at 17:44

1 Answer 1


I am still unable to comprehend your question clearly but based on your comments, it looks like you are looking to replace the Publish States from a restored database.

If you do NOT have to republish your entire content, you can try to use the Convert-TcmPublishStates from HERE. I suggest review the options available and test it in a lower environment before trying it out in production.

If you have to republish your content due to other framework updates involved, you will have to republish the content once the restore is completed again for production.

Hope it helps!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.