Prerequisites for Copying Objects Between Projects

• To use Object Manager to copy objects between projects, you must have the Use Object Manager privilege for both projects. You do not need to have ACL permissions for the objects you are migrating.
• To create an update package, you must have either the Use Object Manager privilege or the Use Object Manager Read-only privilege for the project from which you are creating an update package.
• If you want to migrate objects between projects with Object Manager, MicroStrategy recommends that those projects have related schemas. This means that either one project must be a duplicate of the other, or both projects must be duplicates of a third project. For information about duplicating projects, including instructions, see Duplicate a Project.
• To move system objects between projects that do not have related schemas, the projects must either have been created with MicroStrategy 9.0.1 or later, or have been updated to version 9.0.1 or later using the Perform system object ID unification option. For information about this upgrade, see the Upgrade Help.
• If one of the projects is updated to a new MicroStrategy release, but another project is not updated, you cannot move or copy objects from the project using the updated version of MicroStrategy to the older version. However, you can move objects from the older version to the updated project if the older version is interoperable with the updated version. For detailed information about interoperability between versions of MicroStrategy, see the Readme.