Checklist for 11i Migration Decision
Yes No Business Change Mandatory re-Implement Upgrade Historical Data Upgrade or Convert re-Implement Order Entry re-Implement Upgrade Hardware Change Probable re-Implement Upgrade Downtime tolerance low re-Implement Upgrade MSOBA -> Multi-Org re-Implement Upgrade
The Migration method has the following steps:
Category 1-3 Pre-upgrade steps include Rapid Install Category 4 11.5.x maintenance pack Category 5-7 Post-upgrade
How Does a Migration Differ from a re-Implementation? · The migration converts the data, data structure, applications programs and other objects into the new Release 11i objects. · Setups will be converted in a migration.
· The "re-Implementation" or "new install" method is like an implementation. · This can be an opportunity to revisit current business practices and compare them to "best practices" · A change in the business (COA) may make a "new install" mandatory. · Hardware changes would probably require a "new install". · Gap analysis should be performed with R11i · "New install" required to consolidate multiple instances and implement Multi-Org · "New install" generally requires less downtime during cutover.
Common tasks for both methods · Time from functional users is required to: cleanup List of Values, clean any old setups and perform testing · Customizations need to be documented, customizations could be lost
|