SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Using the managed metadata service with SharePoint 2010, is it possible to synchronize term sets across different farms (or to export an existing term set to CSV so it can be imported on another farm)?

share|improve this question
up vote 3 down vote accepted

Does help you?

You can try also

share|improve this answer
Those are both awesome. Thanks! – Sean Earp Apr 12 '11 at 22:54

Maybe you would find this helpful:

To be honest you could probably knock up a PowerShell script to extract a termset using the object model fairly quickly - but if this works then why reinvent the wheel.

share|improve this answer

We recently moved our term set from test to production simply by attaching the managed metadata database on our production site and moving it along with our content database.

The reason this approach was chosen was, that the users had already starting filling in content in the test environment. Be aware that any import/export solution like the one on codeplex will detach any existing term usage on the content database. For example if you use the taxonomy to tag up documents, the data will stay after migrating the content database, but if you just import the existing terms rather than move the taxonomy database, the items on the documents will be read-only since the lists/TaxonomyHiddenList wont be able to identify the "new" terms as they have completely different GUIDS than the original terms.

Note that this is only an issue if you move both content database and terms from one farm to another, not if you move it to a clean content database that doesnt use the terms yet!

Remember to point to existing taxonomy database when creating a new service application

share|improve this answer
This is the process we use, bring down both databases and then relink the Term Store URL to the local environment after attaching both databases. Works great for us! – MichaelF Apr 19 '11 at 14:26

Another possible approach (with source code) here: Exporting taxonomies from a Microsoft SharePoint 2010 Term Store

share|improve this answer

Have a look at MatchPoint for SharePoint. It provides a TermImporter with various sources like Sql databases, Active Directory, SharePoint lists or any other custom source and it even keeps the managed metadata synchronized.

share|improve this answer
Just a warning that spam is not welcome here. It's OK to advertise your product where it answers a question, but you must disclose that you work for the company in the post, and participate elsewhere in the site without advertising. – Alex Angas Apr 14 '11 at 22:52

Yes, using 3rd party tools like Taxonomy Manager for SharePoint 2010:

enter image description here

You can try here:

Thanks, Frank

share|improve this answer

Yes. You can use a SharePoint Add-In like ServiceAware Term Store Sync to do either manual or scheduled synchronization. There is support for both SharePoint 2013 and SharePoint Online in Office365.

enter image description here

You can download a fully functional free 30-days trial from


Charlotte, ServiceAware

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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