Banner Phase Zero is needs, data, process, and people before Navigate-to-SaaS. Skip it and higher education relocates on-prem Ellucian Banner mess (customization debt, dirty SIS data, unclear owners) into Banner SaaS under a vendor clock.
If you run Banner on campus today, you are not choosing a greenfield SIS. You are deciding how not to import twenty years of local modifications, orphaned codes, and tribal process into Ellucian’s SaaS lane. Avero Advisors does this work buyer-side and vendor-neutral. We do not sell Ellucian.
That is a different problem than “should we leave our legacy SIS.” You are already in market. The product path has a name (Navigate-to-SaaS, Banner SaaS) and the sales motion has a letter, a milestone plan, and a go-live that looks firm until you ask who built it from your data and your staffing reality.
What Phase Zero means
Phase Zero is the work that makes a Banner on-prem to SaaS move honest. It is not a kickoff. It is not a workshop theater day. It is not Ellucian’s methodology with a nicer name.
Needs, data, process, and people, in that order, before Navigate-to-SaaS starts burning calendar.
Needs are what the institution actually requires, written without Banner module names. Data is Banner SaaS data conversion readiness with named owners, not a shared inbox. Process is the workarounds and shadow systems that still close the books or clear a hold. People are decision rights: who can say yes when SaaS configuration and campus practice disagree.
Skip any of the four and you are not modernizing. You are relocating the mess. Dirty student and finance records move to SaaS without complaining. Unclear owners survive mock conversion. Customization debt that felt inevitable in 2012 becomes an exception queue that never drains.
Start at Zero still holds when you are already on Ellucian Banner. Especially then. The current instance is not the requirement. It is one dated answer to it. Why government organizations need to modernize their ERP systems is the same argument in a different wrapper: the platform is not the strategy.
Why Navigate-to-SaaS starts a clock
Navigate-to-SaaS is Ellucian’s motion for shops already on Banner. It is a program with mocks, milestones, and a go-live that will be treated as physics once it is on a slide. The vendor’s incentive is coherent: reach their definition of cutover, invoice the work, move to the next campus.
Your incentive is different. A registrar who can run add/drop week. A controller who trusts the books. A CIO who did not bet the brand on a date picked before anyone inventoried customization debt.
Those incentives only align if Phase Zero happens before the Navigate-to-SaaS program owns the clock. Once mocks are scheduled, “we’ll clean in parallel” is how data hygiene dies. Once the letter is signed, manufactured urgency from a support, commercial, or roadmap date crowds out the only work that changes the institution: deciding what you need, who decides, and what you will stop doing.
Go-live is not readiness. A green checkmark on a mock conversion is not proof that shadow systems went away. Banner SaaS constrains customization. It does not invent process owners. It does not clean PIDM collisions, chart-of-accounts drift, or aid packaging rules that only three people understand. Treating cutover as modernization is how you get a prettier portal sitting on the same operating floor.
If your RFP for an implementation partner or PMO asks only for Ellucian certifications and a timeline that matches the letter, you are buying timeline theater. Run Phase Zero as a buyer-side workstream (ERP advisory and, when the program is live, buyer-side PMO) with its own gate. The cheapest moment to discover you are not ready is before Mock 1, not after Mock 5. The same failure mode shows up outside Banner; see seven pitfalls to avoid during system implementation.
Needs: write them without Banner module names
If the needs list describes the incumbent, you will buy the same thing in the cloud.
Write what the institution must be able to do: register a student, package aid, post a journal, produce a board report, clear a hold before commencement. Do not write Banner form names, modification numbers, or “we need the same custom job that runs on Sunday.” That list is a museum of customization debt, not a requirement.
Avero’s test is simple. For each top complaint, can you name the actual constraint (in the work, not in the product)? If the answer is a shrug or a vendor slide, it is a configuration or process problem. It will follow you into Banner SaaS.
Needs work is also how you decide whether Navigate-to-SaaS is the right motion versus managed cloud first, a phased module path, or a replacement SIS. Viability is not “Ellucian is big.” It is whether this program can finish without lying to itself, given your academic calendar, bargaining, and freeze windows.
Do this on paper, with cabinet time, before anyone schedules mock conversion. The Banner Phase Zero checklist is built for that conversation.
Data: named owners for Banner SaaS conversion
Banner SaaS data conversion readiness is not a weekend script. It is a decision about which dirt you refuse to host in SaaS.
Name a human (not “the Registrar’s office,” not “IT”) for student identity and person records, chart of accounts and fund structures, holds and attributes, packaging rules, and historical conversion scope: what moves, what archives, what dies. If ownership is “shared,” the mock will fail in a meeting, not in a lab.
Hygiene first, student and finance first. PIDM collisions, duplicate persons, drifted funds, and aid rules that live in someone’s head do not get cleaner because the instance is multi-tenant. They get promoted.
Mock conversion only tests what you told it to test. If the inventory of interfaces, ODS/EDW, and shadow extracts is incomplete, Mock 3 is where the surprise lands. Put the backlog in writing with owners and a definition of “clean enough” before Ellucian’s program starts the clock. Score that honestly on the Navigate-to-SaaS readiness scorecard, also called a Banner SaaS readiness scorecard when the cabinet wants a plainer name.
Process: workarounds and shadow systems
Banner never quite owned the last mile. Commencement lists, billing holds, and board reporting still run in Excel. Someone still knows a Banner 8 path that the rest of campus has forgotten. Those workarounds are the process.
SaaS will not absorb them automatically. It will refuse some of them. The Phase Zero job is to decide what dies, what is rebuilt as configuration, and what never belonged in the SIS.
Inventory the work that actually happens: registration, billing, FA packaging, procurement, HR actions, integrations promised versus built. If it is not on the inventory, it will surprise you in a mock. Dual entry and exception queues expanding after go-live are not a training problem. They are process you declined to name.
This is also where customization debt gets counted. What you built on-prem that Banner SaaS will not carry has to be retired, replaced, or used as a reason to refuse the move until it is gone. Hoping the integrator “handles it” is how you relocate the mess.
People: decision rights before mock conversion
Configuration choices will arrive faster than your shared-governance calendar. Name the owners for student, finance, FA, HR, and integrations before the SI fills the parking lot. Ambiguity here is how timelines slip while everyone stays “aligned.”
Decision rights are not a RACI poster. They are who can freeze scope, who can say no to a bolt-on, and who owns the call when Ellucian’s timeline and the academic calendar disagree. Provost and registrar sponsors have to be in that map, not copied on it.
Staffing is a Phase Zero finding, not a mid-project surprise. Day jobs do not pause for mocks. If you cannot free the analysts who own registration, billing, and GL close, you are not understaffed on the vendor side. You are understaffed on the buyer side.
Avero Advisors sits on that side of the table. Higher education ERP advisory here is not an Ellucian partner motion. Banner SaaS advisory for higher education means we are paid by the institution. No licenses. No referral fees. The recommendation costs the same whichever way the findings point.
The Banner Phase Zero checklist and Navigate-to-SaaS scorecard
If you run Banner on campus and the SaaS clock is already wound, start here, not with Mock 1.
The Banner Phase Zero checklist is the four-section printout: needs, data, process, people. Fill it with your cabinet. Request it by email. It is not a public PDF.
The Navigate-to-SaaS readiness scorecard is the self-score: customization debt, data owners, mocks, decision rights. Same gate. Same rule: we email the file.
Both sit next to Avero’s higher education practice: colleges, universities, and systems already on Ellucian Banner, and peers. Buyer-side. Vendor-neutral.
Needs, data, process, people, then Navigate-to-SaaS. Phase Zero is not delay. It is how you keep the pen when someone else brings the clock.
Start at Zero.
Subscribe at avavero.substack.com, or read Start at Zero.
FAQ
What is Banner Phase Zero?
Banner Phase Zero is the buyer-side work higher education should finish before Navigate-to-SaaS: needs written without Banner module names, data conversion readiness with named owners, process (workarounds and shadow systems), and people (decision rights and staffing). It is Ellucian Banner SaaS Phase Zero in plain language, not a vendor kickoff.
Is Banner Phase Zero still needed if we stay on Ellucian?
Yes. Staying on Ellucian and moving on-prem Banner to Banner SaaS is still a program. SaaS constrains customization debt; it does not clean SIS data or invent owners. Phase Zero is how you avoid relocating the mess into the same vendor under a new clock.
What if we skip Phase Zero and go straight to Navigate-to-SaaS?
You relocate on-prem Banner mess into SaaS. Dirty data is promoted. Mock conversion checks the wrong things. Decision rights show up as slipped dates. Go-live looks green while shadow systems expand. The clock is then Ellucian’s, not yours.
Is Avero an Ellucian partner?
No. Avero Advisors is buyer-side and vendor-neutral. We do not sell Ellucian licenses, we are not an Ellucian partner, and we take no referral fees. Higher education ERP advisory and Banner SaaS advisory here are paid by the institution.
AV, Avero Advisors