The biggest mistake folks make when migrating is barreling into the migration without doing any prep work in Microsoft FRx and Management Reporter 2012. They download Management Reporter, install it, install the migration wizard and run the migration. If you do this, you are going to be frustrated and unsuccessful. I guarantee it.
Our support folks have written a great knowledge base article walking you through step by step the things to do to prepare. The highlights are:
The majority of support calls our support teams receive could’ve been avoided if the steps above were followed.
Once you’ve done the all the prep work, it’s time to install the migration wizard. The migration wizard is part of the Management Reporter 2012 installation package. It’s not a separate download as it was in the past. You can find the Management Reporter 2012 install here. On the launch page for the Management Reporter installation, you’ll see options for installing the migration wizard and viewing the migration guide. The migration guide is a great resource for installation instructions as well as data preparation. Read it before installing!
Now that you’ve prepped both Microsoft FRx and Management Reporter 2012, read the documentation and installed the migration wizard, what can you expect next?
The number of companies and building blocks you have will determine how long the migration actually takes. (Another great reason to get your Microsoft FRx house cleaned out before you move!)
A couple of questions I get asked regularly when presenting migration sessions are:
I’ll answer both questions at the same time. In some cases, the functionality has been rethought and implemented in a new way in Management Reporter 2012. In other cases, we are relying on you to tell us if it’s a feature we should include in future releases of Management Reporter.
Items that don't migrate:
Company connection information
Web publishing settings
Currency Translation Rates
After migrating, run Management Reporter 2012 and Microsoft FRx side by side. You’ll want to make sure your reports all generate and everything you expected to be in Management Reporter 2012 is there.
Now that you know what to do to prepare and expect, you are ready to migrate!
Great blog, Jill. Very useful and helpful information. Thanks!
Can you just import Rows, Columns and tree from an exported FRx 6.7 Spec Set from another system?
There are changes in the format of a .tdb and a .tdbx. You should not try to import an FRx specification set directly into Management Reporter. You should go through the Migration Wizard if possible.
I have 20 companies set up and are used in FRx 6.7 sp11. Of these companies 5 might share one specset and 3 use another specset. I only have 9 specsets. How will Migration work for me? Should I setup new specsets for each company and export the "company related" building blocks from the shared specset into the newly created specsets?
Also, in Management Reporter 2 you couldn't have any building blocks named the same. We do have instances where a column could have the same name as a row in one specset. Is this still an issue in Management Reporter 2012 RU2?
Please incorporate row linking and allow more than one row definition per tree.