Migrating megamenu-taxonomy from one instance to another ?

[Mariano1]

Hi team

I've built a quick taxonomy on a dev instance for a client and right now I'm at the part where I need to migrate it to test. I've been finding it hard to migrate it properly to be honest. Some records don't get captured on the update set and I'm starting to think that there's no way to migrate it and that I would need to replicate it again on each instance.

Anybody that has done it before?

Thanks!

[Community Alums · Accepted solution]

Hi @Mariano ,

When you migrate something as part of update set , remember one thing any data or records won't get captured in the update set. so the only option is to import and export via XML.

Also, as part of the best practice in Employee center:

To enable curated experiences, customers need to build a unified taxonomy, which can take some effort on the customer end to do in its entirety. Customers have two options to proceed:

Option 1: Invest early in building a unified taxonomy for their organization: To do so, we recommend customers build a team (preferably including someone with taxonomy design skills and someone with content ownership) to help with the unified taxonomy for their organization. The team tasks include a) clone the out of box taxonomy topic structure and modify it based on the terminology familiar with their employees and b) tag their existing content (including catalog items, KB articles, quick links, campaigns, and videos) with the topic structure.

Option 2: Pick a small set of (3-5) topics and build curated experiences around them: Many customers who are not quite ready to tag their content into one unified taxonomy may want to start small by selecting only a few topics and tagging content only for those. These topics should be the ones their employees are most interested in and preferably one of the topics shipped as part of the OOB taxonomy. Customers would have to update the taxonomy associated with the portal with the topics they choose to enable curated experiences using those topics.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[Community Alums]

Hi @Mariano ,

Any update to this ?Any follow-up required? if not

Kindly mark the answer as Correct & Helpful both such that others can get help.

Thanks,
Sandeep

[Santoshi5]

Hey Sandeep,

Thanks for the above Article it's really helpful,

I have a few questions on this Taxonomy 

1) Is it mandatory to keep the clone version of Taxonomy? or the best way to keep the scratch creation of this Taxonomy and use it in the portal, because our portal is also become scratch we are not using esc OOB portal.

2) Which application we need to keep for this ?, as per my investigation if we cloned we need to keep Employee taxonomy application but if we are creating from scratch we can keep it in Global Application.

3) Is it good to map all the Catalog Items under this Taxonomy Topic ?we have almost more than 1000 + catalog items tagged in different categories ?

Please help me with this clarification.

[Alicia Haag]

I'm especially stayed aware of the article and I will get many benefits from it. Subsequently, thank you for sharing it. My Payments Plus Login Page