MOSS 2007 migration between different languages doesn’t work!


A few moths I posted on this subject and due to testing these situations, I told you that the direct migration between different MOSS regional products was not possible because the Export/Import functionality is dependent of the language ID (Migration in MOSS – the language issues and Problems in MOSS Land? well, join the club!) and this process simply is not supported by Microsoft.

Nevertheless in the documentation (It has been updated to change this specific issue!) we could have a different approach using the same MOSS language server and Language Packs, this meant that in a English MOSS server we could have an English site collection and Migrate (Export / Import) to a different language depending on the installation of the correspondent Language Pack. The reality is that this doesn’t work either, the situation is the same as the migration between different regional products, the sites are still dependent of the language ID.

This issue was presented to Microsoft and reached the Product team that acknowledge that this was a documentation error and the documentation was corrected (it was added a note in the Migrate content by using import/export topic saying that “You can import sites only into site collections that are using same language as the exported site“).

This post is just to raise awareness to this specific migration issue, because as an early adopter i encountered these problems.

Computer developer/consultant from Portugal. You can find me at ricardo.magalhaes@gmail.com

Tagged with: , , , , , ,
Posted in Sharepoint
4 comments on “MOSS 2007 migration between different languages doesn’t work!
  1. Steve says:

    Thanks for your post. Just tried it myself and could not believe what stsadm.exe told me:

    Cannot import site. The exported site is using language 1033 but the destination site is using language 1031. You can im port sites only into sites that are using same language as the exported site.

    We are expanding world wide and need to replicate applications to other branches but want to use the local language instead of English.

    I am so pissed off! We need to migrate everything by hand now. Thanks for noting, MS!

  2. HI Steve,

    I must agree with you that the situation is really annoying, but there are 3rd party tools to help migrate content between languages, so not all is lost . . .

    This situation seems to be something that MS was planning to do but didn’t have time to finish.

  3. Robert Graauw says:

    thnx for this. I was gonna try to see if it works but reading your blog prevented me from wasting any time on this mathod.

    Do you know any third party tools that will do this??

  4. Miguel says:

    Hello!

    We are just in the process of importing the companyweb from a SBS2003 server to a SBS2008, and we are getting the dreaded message…

    “Cannot import site. The exported site is using language 2070 but the destination site is using language 1033. You can import sites only into sites that are using same language as the exported site.”

    Is there currently any fix to this? You mentioned there are 3rd party tools to migrate content…? Which ones?

    Thanks for all your help!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: