We are just running through quite a few scenarios for upgrading our beta clients from CRM 4.0 to CRM 2011.
The first pass of the upgrade process went OK, however, it was a little slow. We made some changes to the source CRM 4.0 database (via the UI) and tried to re-upgrade/import this database into another tenant on the CRM 2011 system using the following:
CRM 4 Server
- Change the CRM 4.0 config.
- Backup the database
CRM 2011 Server
- Move the backup to the CRM 2011 database server.
- Restore the database to another name.
- Import the tenant using another name.
We wanted to do this to minimise downtime for the data migration consultant. The end result was proposed to have the dm preparing against the earlier upgrade and the dev team tweeking the import/upgrade process.
However, the error “you have already imported and upgraded this organisation and cannot perform the operation again” was displayed from the Import Manager:
A few “bings” presented the same result – You can’t re-import the same CRM 4.0 database – and atleast have more than one tenant.
The solution we came up with works like this:
CRM 4 Server
- Change the CRM 4.0 config.
- Backup the database
- Restore the bak to another database name
- Import the organisation to another name
- Backup the new database
CRM 2011 Server
- Move the backup to the CRM 2011 database server.
- Restore the database to another name.
- Import the tenant using another name.
The import process checks for the OrganisationId, the trick is to get a new organisationid – this can be achieved by making a “clone” of the CRM 4.0 tenant using CRM 4.0 Deployment tool