Frequently Asked Questions
- Q: How does this project fit into SLU's overall ERP strategy?
- A: This project is the first step in a multi-phase initiative to modernize the Ellucian Colleague application. During the migration to Ellucian Cloud Hosting, we will be moving Colleague to new servers and infrastructure. While little will change for most users in the short term, these important changes help lay a foundation for future improvements to the Colleague system and how we use it at SLU.
- Q: What comes next after we've moved Colleague to the cloud?
- A: Once the migration is complete, Information Technology in collaboration with administrative and academic offices across campus can begin examining currently unused Colleague features and functionality we may want to activate and implement in the near future. These activities, to be planned and implemented in future projects and initiatives, will enable us to better leverage the Colleague system in direct support of the University’s institutional mission and strategic goals.
- Q: Who is performing testing?
- A: The Functional Leads assigned to the Project Team will coordinate testing for their areas based on their identified requirements. For more information on who is working on the project, please see our page on the Project Team.
- Q: What browser is recommended when working with Ellucian Colleague?
- A: Microsoft Edge Chromium; Safari; Firefox; and Chrome
- Q: When will this project Go-Live in our production systems?
- A: Our final migration to the Ellucian Cloud Hosting environment is scheduled for Friday, July 29, 2022 through Tuesday, August 2nd, 2022.
- Q: I noticed that the Go-Live is scheduled for four days. Why so long? Will Colleague be unavailable this entire time?
- A: To complete the final movement to the Ellucian Cloud Hosting environments, we have designated a four-day window. This will allow the project team the time required to complete a final backup of our Colleague systems and databases, move that into the Ellucian Cloud, complete the final setup on the new systems, and then perform a final round of User Acceptance Testing (UAT). The majority of the four days are dedicated to UAT so that our functional areas can confirm the systems are working as intended. We've also allowed for extra time to address any problems we might experience. Allowing extra time to address any unexpected problems that might come up last minute is a project management best practice.