DevOps clone best practices

[Rob50]

Does anybody have any recommendations on cloning best practices other than preserving the DevOps tables. There are multiple different tables, and not all documented therefore I thought there may be an easier way to maintain the integrations in the sub-production post clone.

Cheers,

R

[Yousaf]

Hi Rob,

Check these links 

CLONE - Frequently asked Questions (FAQ)

Best Practice For Cloning During Long-Term Projects

Cloning & upgrade best practices

Cloning Resources Page

10 technical best practices for a seamless ServiceNow upgrade

Post-Cloning Checklist

http://blog.cloudsherpas.com/cloud-implementation/servicenow-admin-101-system-clones-best-practices/

Mark Correct or Helpful if it helps.

Thanks,

Yousaf

[Dionbecu · Accepted solution]

This has been a pain point for us as well. It looks like the finally put out information in the docs site about this. I hope it helps.
https://docs.servicenow.com/bundle/washingtondc-devops/page/product/enterprise-dev-ops/reference/dev...

[Neeljy]

You might consider using clone target rules to preserve key integration-related tables beyond just the DevOps tables. Additionally, leveraging scripts or data policies to automatically restore necessary configurations post-clone could help. If your integrations rely on external credentials or connections, make sure to validate and update them after cloning. Have you identified any specific integration failures after a clone?