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.