Suppose the Registrar’s team uses a local job to flag prerequisite overrides for review. The developer can show when the job runs, but nobody has written down which overrides staff check or what happens when the job misses one. Before deciding what to do with the code, have the Registrar describe the task and show the expected result.
Find the rule behind the customization
Ask a developer and a functional owner to review each item together. Include local jobs, modified forms, reports, scripts and manual steps that depend on their output. Record the item name, who uses it, when it runs and where its result goes. Ask the owner to show an approved requirement or a sanitized example of the result staff rely on. Check a full academic cycle before treating a seasonal job as unused.
Confirm the source release, the contracted target and the deployment model before anyone proposes a replacement. Ellucian describes the University of Lancashire’s project as a phased move to Ellucian Student powered by Banner. Use your institution’s own project scope to confirm the applicable modules, licenses and access. A managed hosting move or an on-premises upgrade can involve different constraints.
Mississippi State University’s September 2025 request for proposals asked for help reducing unnecessary Banner customizations and returning to delivered functionality where possible. The request describes the university’s objectives. For your own review, give each customization one line in the register and ask the office that owns the work to confirm the need.
Choose a disposition the owner can test
Have the Registrar state the prerequisite rule, the override process and the point at which staff need the list. Ask the implementation lead to show any delivered option in the agreed test environment using the correct role. Run cases with an approved override, a denied request and a course change. Compare which students appear on the list and whether staff can tell who approved the override.
If a delivered option leaves a gap, confirm whether the institution still needs that part of the process. Where it does, ask the architect to confirm a supported method for the contracted target and identify the person who will maintain it. The functional owner accepts the result. The architect confirms that the agreed deployment supports how it is built.
| Proposed decision | What staff check | Who approves |
|---|---|---|
| Retire the item | Check scheduled runs and downstream use across the relevant academic cycle. Confirm whether records or outputs must be retained. | Functional owner with records management and IT |
| Use delivered functionality | Run the same workflow under the intended role. Compare the records and expected exceptions with the approved requirement. | Functional owner with the application lead |
| Change the staff procedure | Have staff complete the task using the new procedure and show where the approval or exception is recorded. | Functional owner and supervisor |
| Build a supported replacement | Confirm the supported method, access and ownership. Test expected output, timing and how staff handle a failed run. | Architect and functional owner |
| Hold the decision | Write down the unanswered question, who will resolve it and which date or release decision it affects. | Implementation sponsor and functional owner |
- Step 01Name the task
Ask staff what they do with the output and when they need it.
- Step 02Check the target
Run the task using the agreed role and test records.
- Step 03Record the decision
Write down what changes, who approves it and what still needs a test.
- Step 04Repeat before cutover
Confirm the result and who handles a failure after launch.
Keep the register current as requirements change
Give each row an owner, a decision date, an expected result and a test link. Keep any approved workaround with the person responsible for it and an end date. When staff request a change after the inventory is agreed, record the reason and update the test before accepting the change. Seton Hall University reported a temporary pause on most new core system enhancements in March 2026 during its Banner SaaS preparation. That was a local decision. Set your own change rules with the offices that depend on the work.
If an approved external AI tool can help, give it approved descriptions and requirement IDs without student records, credentials or restricted code. Ask it to suggest groups of similar items and flag missing owners or unclear dependencies. The developer checks the suggestions against the job inventory. The functional owner verifies each requirement and accepts only the rows that describe real work. Add the checked rows to the register for staff to decide.
References: [3]
Bring the open decisions to the cutover review
Ask each office to bring its completed test results and any item it still relies on. If the replacement for a registration job fails, name the affected task, the registration date and the person who will retest it. Give the sponsor the choice the team needs, such as approving a tested temporary procedure or moving the affected work to a later phase.
Save the approved decisions with the cutover plan. After the first registration cycle, have the support owner review any temporary steps and confirm which ones can end. If you need help getting the Registrar and IT through the first set of decisions, start with the register and the tasks that have the earliest deadlines.
Sources
- University of Lancashire Takes a Strategic Path to SaaS — Ellucian (accessed )
- RFP 26-10 — Consulting/Professional Services for preparing for a SaaS ERP (Ellucian’s Banner) — Mississippi State University (accessed )
- Banner SaaS Migration Reaches New Milestone — Seton Hall University (accessed )
Related reading
- Cloud & SaaS Migration
From Banner Student to Ellucian Student: a modernization readiness checklist
Before setting a migration date, list the jobs, reports and interfaces staff rely on. Assign someone to check each one and confirm how it will work in the new system.
- Integration & Ethos
Before moving to Ellucian Student: map the interfaces that must keep working
Find the jobs, files and manual uploads that connect Student to other systems. Have staff confirm who uses each transfer, when it must arrive and what must change before cutover.
- AI & Automation
Use AI to draft student-lifecycle tests for an Ellucian Student migration
Give AI approved requirements to draft test cases. Have the Registrar, Student Accounts, Financial Aid and IT check the steps and expected results, then run the tests in the agreed environment.
- Related service
Cloud & SaaS Migration
Readiness, planning and cutover for institutions moving Ellucian and adjacent platforms to the cloud.

