new instance initial data import

[craigsnowadmin2]

For a new implementation of customer service  - foundation data  as the first application module to implement. Isn't it  better  to import the data ,  in production and then clone it to lower sub production instances . Any issues or suggestions

[Gunjan Kiratkar]

Hi @craigsnowadmin2 

The main purpose of the Non production instances are to load data and test on that whether we are getting expected output as per our requirement or not. If you do the import directly on production instance it will be completely mess and not a good practice at all. As it is the live instance we can't directly import or make changes in that.

Best practice is always do import /load data on non prod instance then you can move the XML files to the production so that sys_id remains same throughout the different instances.

Hope it helps.

[craigsnowadmin2]

Incase of an existing live production instance , yes we Usually always import in development instance and then validate to move to production . But if its a new  production blank new instance , not live yet.

[Gunjan Kiratkar]

Hi @craigsnowadmin2 

Still that is not a good practice. Because the purpose of instance is changing by doing this and proper testing is not possible by doing this as lot of test data is getting created.

I will recommend to go with below pathway:-

development - test - production 

[craigsnowadmin2 · Accepted solution]

For latest release , I was able to find myself answers in another  thread on new implementation in the community and also in ITSM guided setup  for new customers and documentation per ServiceNow .