Employee Center - moving Connected Content between instances

Michal Sadowski
Mega Sage

Hi Employee Center superstars,

I'm getting ready for the migration project from Service Portal to Employee Center and just wanted to double check on one of the doubts I have that may impact the approach.

It's related to Connected content. Is this something you would start in Dev instance and then migrate up all the way to Prod for the initial implementation? Is this migratable in update sets or as XML imports or some other way? Any other thoughts on what to watch out for when moving Connected Content between instances?

Kind regards 

1 ACCEPTED SOLUTION

No problem, 
Yeah I just tested this by moving some connected content from dev to test and you're right it will work using xml. 
I would say it is not risky if you're confident that the data is correct. Additionally, as it is just data it is unlikely to break anything. 
if you have 2 sub production instances then you could migrate the data from dev to test before moving it to prod/live. 
Thanks
Alex

View solution in original post

9 REPLIES 9

Alex319
Giga Guru

Hi Michal, 
I would always suggest creating the connected content in DEV initially to ensure you are happy with how your content appears on the Employee Center. 
However, I believe you will have to manually create the connected content relationships when you move your data from DEV>TEST>PROD. 
Having said this your catalog items should be migrated using update sets, so the process is still fairly quick. 
As you can see in the picture below. the catalog item doesn't need to be recreated and can just be selected whilst connecting the catalog item to a particular topic:

Alex319_0-1670326483396.png

I hope this helps

Alex

Thanks for this. So just wodering - assuming all catalog items, knowledge articles and quick links exist with the same sys_id across instances, looks like Connected content records could be simply exported as XML from Dev and imported in Test and/or Prod with no need for manual double work...

Or is this risky for one reason or another?

No problem, 
Yeah I just tested this by moving some connected content from dev to test and you're right it will work using xml. 
I would say it is not risky if you're confident that the data is correct. Additionally, as it is just data it is unlikely to break anything. 
if you have 2 sub production instances then you could migrate the data from dev to test before moving it to prod/live. 
Thanks
Alex

You're a legend Alex. Thank you. Marking this as the solution to my question.