Some steps

1) Create a target app with the same name/same plan types
2) Create the dimensions (just the dimensions, no descendants) within that target app
3) Migrate away

I can't remember if the LCM docs explicitly say that the dimension stubs need to be created or not. Probably it does, else I wouldn't have figured it out.

Anyway, it works pretty nicely. The whole thing can be scripted if you want to automate the process.

Remember that Essbase data is *not* migrated with this release.

Regards,

Cameron Lackpour