Staring this kick off with this as the base:

That’s a great move—migrating from on-prem DB2, Oracle, and Progress databases to Infor hosted in AWS. Since Infor is built on AWS, you’ll get scalability, security, and AI-driven enhancements, but a successful migration requires careful planning.

Key Considerations for Your Migration Plan

1. Understanding Your Current ERP Landscape

Before anything else, you need a clear picture of your existing systems. A few questions to get us started:

• Which ERP systems are you running? (E.g., Lawson, M3, Baan, or custom-built solutions)
• Are all your databases on-prem, or do you have hybrid setups?
• Any legacy customizations or third-party integrations in play?

2. Database Migration Strategy

Since you’re working with DB2, Oracle, and Progress, each will have different challenges:

• DB2: Will require specific migration tools. Are you running DB2 on IBM iSeries (AS/400) or z/OS?
• Oracle: Are you using Enterprise, Standard, or RAC? How dependent are your apps on PL/SQL procedures and triggers?
• Progress: What version? Are you using OpenEdge with 4GL business logic?

AWS offers tools like AWS Database Migration Service (DMS) to migrate data, but the approach depends on how Infor expects the data to be structured.

3. Data Cleansing & Transformation

• Do you need to archive or transform historical data before migration?
• Are you migrating all transactions or just master data (customers, vendors, products, etc.)?

4. Application Modernization

• Infor’s cloud-based ERP model may require some of your business processes to change. Have you reviewed what features or processes need reconfiguration?
• What custom business logic, workflows, or reports must be rebuilt?

5. Security & Compliance

• FedRAMP, ITAR, SOC-2, HIPPA, or other compliance requirements are met.
• Your identity & access management (IAM) strategy aligns with AWS security best practices.
• Data encryption policies (Infor encrypts data, but any specific security mandates?)

6. Cutover & Go-Live Planning

• Will you do a phased migration (modules one at a time) or a big-bang approach?
• How will you test & validate data post-migration?
• What’s your fallback plan in case of delays or unexpected issues?

Next Steps

Once we answer these, we can build a detailed roadmap with timelines, required resources, and a risk mitigation plan. Let me know where you’d like to dive deeper!