Sage 1000 end of life

Month 1: Stakeholder alignment and project kickoff. 

• Conduct initial meetings with key stakeholders. 
• Define project objectives, scope, and expected outcomes. 
• Set up regular communication channels and reporting processes. 

Month 2: Requirements gathering for new system. 

• Document current business processes and workflows. 
• Identify system needs, gaps, and desired improvements. 
• Draft a detailed requirements document. 

Month 3: Research and shortlist new solutions. 

• Research potential ERP solutions based on business needs. 
• Engage with industry peers for feedback on their ERP experiences. 
• Shortlist 3-5 ERP vendors for further evaluation. 

Month 4: Attend supplier demonstrations. 

• Schedule and participate in detailed product demos. 
• Engage end-users for feedback on demoed solutions. 
• Document strengths and weaknesses of each solution against requirements. 

Month 5: Supplier selection & contracts. 

• Finalize ERP vendor based on demo feedback and alignment with requirements. 
• Negotiate contract terms, pricing, and support agreements. 
• Secure legal and financial approvals for the vendor contract. 

Month 6: Develop a detailed migration plan. 

• Plan out the entire migration process with timelines. 
• Define milestones, checkpoints, and deliverables. 
• Allocate resources, both human and technical, for each phase. 

Month 7: Finalise project team and key roles. 

• Identify key team members across IT, finance, operations, etc. 
• Assign specific roles and responsibilities for each team member. 
• Conduct a project kick-off meeting with the entire team. 

Month 8: Data preparation and data cleanup in Sage1000. 

• Review data quality and identify inconsistencies or errors. 
• Start data cleanup activities. 
• Plan data migration strategy, including data mapping and transformations. 

Month 9: Sign off on solution design blueprint for new system. 

• Review the ERP system’s proposed design and configurations. 
• Ensure alignment with business processes and requirements. 
• Obtain sign-off from key stakeholders. 

Month 10: Configuration of system in line with blueprint. 

• Start system configuration based on the approved blueprint. 
• Regularly review configurations against requirements to ensure alignment. 
• Set up initial user roles and access permissions. 

Month 11: User training and preparation for testing. 

• Develop a user training plan and materials. 
• Start training sessions for key users and end-users. 
• Prepare test scenarios and scripts for user acceptance testing. 

Month 12: Conduct user acceptance testing. 

• Execute test scenarios in a controlled environment. 
• Document any issues or gaps and work on resolutions. 
• Obtain user feedback and make necessary tweaks to the system. 

Month 13: Go live with the new ERP system. 

• Finalize data migration from Sage1000 to the new ERP. 
• Ensure all configurations are in place and validated. 
• Monitor the system closely for any issues during the initial days. 

Month 14: Address any post-go-live issues and optimize processes. 

• Gather feedback from users on any challenges or pain points. 
• Address reported issues in a timely manner. 
• Optimize and tweak processes based on post-go-live learnings. 
   

Month 15: Review project and solidify long-term support plans. 

• Conduct a detailed project review with stakeholders. 
• Document lessons learned and best practices for future reference. 
• Establish long-term support and maintenance plans for the new ERP system.