In this blog post, we will introduce a series of data migration special considerations for your ERP implementation.
Previously, we shared a blog post Oracle Cloud ERP Data Migration Recommendations and Best Practices which is about general data migration. In this post, we discuss additional or special considerations for higher volume data migrations.
The following blog posts by application address these specific recommendations for the objects listed below.
| Module | Data Objects | Recommendations |
|---|---|---|
| General Ledger | Balances, Journals | Convert no more that 2 years of GL balances |
| Purchasing | Suppliers, Requisitions, Purchase Orders | Active suppliers, open POs only |
| Accounts Payable | Invoices | Unpaid invoices only |
| Accounts Receivable | Customers, Transactions, Receipts | Active customers, open transactions only |
| Fixed Assets | Assets, Depreciation | Provide the accumulated depreciation |
| Project Management | Project and Tasks, Budgets, Expenditures, Revenue and Billing Events | Active project and tasks. Summarize cost and revenue balances |
We will share more details on each of the above topics in separate posts (as these are posted, we will update with links):
General Ledger
Purchasing
Accounts Payable
Accounts Receivable
Fixed Assets
Project Management
Conclusion
You must carefully plan and test your data migrations. If you are converting higher volumes for any of the entities listed above, we recommend that you review our recommendations in the above blog posts. We have provided a number of recommendations to help you through this process.