Time is running out for legacy FDM users. Oracle officially retired FDM Classic in favor of its successor, FDMEE. With your next Oracle EPM upgrade cycle Oracle requires you to migrate to FDMEE. Don’t worry; you will want to make the leap to take advantage of the many enhancements that FDMEE has to offer. (Click here for a few reasons why you will want FDMEE.)
Before migrating to FDMEE, administrators (with the assistance of a seasoned consulting partner) have an important decision to make – Which migration method is right for us?
Two Migration Options: Rebuild vs. Migration Utility
When FDMEE was introduced in 2013 with Oracle Enterprise Performance Management (EPM) System Release 184.108.40.206, going from FDM Classic to FDMEE was a rebuild. Last fall, however, the Oracle FDM development team released the FDM Migration Utility to complement FDMEE Release 220.127.116.11.
Since considering your journey from FDM Classic to FDMEE, you’ve probably browsed the Internet for nuggets of information. Our guess is you’ve heard a lot about the rebuild approach and not a whole lot about using Oracle’s FDM Migration Utility.
Our objective with this blog series is simple – Help you decide which migration method is best suited for your upgrade project based on your Legacy FDM application(s), which method is best suited for you. This series is less how-to and more which way. Which path provides the smoothest road to your ultimate destination – FDMEE.
- Part 1 – FDM Migration Utility: System Requirements
- Part 2 – FDM Migration Utility: The Secret Sauce
- Part 3 – FDM Migration Utility: Turn Classic to EE with a Push of a Button?
- Part 4 – FDM to FDMEE: Artifacts and Migration Options
- Part 5 – Rebuild vs. Migration Utility: Pros and Cons
- Part 6 – Legacy FDM to FDMEE: Where to Start