Planning a Migration from ­Oracle EBS to Oracle ERP Cloud?
Tips and Tricks to Help You

David Wright, Global Pre-Sales Manager, More4Apps

All migrations have impacts, not just to your source and target systems. The impact will be substantial with various touch points within your organization. Your project team will need to take into consideration costs, process impacts and resource requirements. Regular communication to business, data security and general IT staff are paramount in your migration project plan.

A key aspect of any migration is what data to take across and what is the most efficient way to make this happen? Key questions include:

  • Are there scripts that I can just execute and extract all the data from my EBS legacy system?
  • What data cleansing tasks should I perform?
  • Where’s the best place to clean the data?

Figure out your approach. Will you migrate or re-implement?

Before making a start, you need to step back and perform an assessment on both your current EBS and proposed Cloud ERP setup.

  • How will you create the key data for your system (accounts, customers, suppliers, items etc.)?
  • How you will extract the data from EBS?
  • Will you import only open transactions or take the entire history to the new system?
  • Is there any data to reorganize or clean up?

Do you keep your old system live or migrate all the history to the cloud?

Data is the life blood for any organization. With migrations, you have multiple options and combinations, each one with benefits and disadvantages.

Option 1: New setup and only uploading balances and open transactions

This is your opportunity to adopt a new chart of accounts, categories and even a new inventory item master.

Option 2: Similar setup, all data

Perform a full migration and do a like-for-like setup; there will be some mapping involved, especially for custom data. Moving anything “non-standard” will be a drain on your project resources and likely increase the cost of the project.

Option 3: Hybrid migration and transformation

You can also decide to upload only a portion of the data for some modules (i.e., only open transactions for AP and PO and just tax years on GL detail) if you are also transforming your chart of accounts. Then this will likely be a combined effort between cleaning your data and also the consulting effort of the migration itself.

Hot Tip: When you are migrating open transactions, it’s always good to try to pay most of your pending invoices and receive all the items still not received on the Purchase Orders.

Cleanse your data now!

Now is a great time for you to clean up what you can before the migration even starts. Your users know and understand the current system and what needs to be cleansed. Cleaning up your current data is a low impact way of preparing for migration that will help de-risk your project and provide your organization with quality data.

There are products available to help you perform the migration from Oracle (Soar) and companies like DataLynx. However, these aren’t end-user-based data cleansing solutions and work best when presented with quality source data.

There are leading, not bleeding edge tools with a proven track record available now for your end users to help improve your chances of a smooth migration.

More4Apps simplifies business processes by providing intelligent data capture and integration solutions. Since 2000, More4Apps has gained more than 20,000 EBS users in over 45 countries, establishing a loyal customer base.