A complete Ellucian Banner / Colleague migration assessment for universities and community colleges. Module inventory across Banner / Colleague Student, Finance, HR, Financial Aid, Advancement and Self-Service; customisation catalog; downstream-integration map; FERPA, Title IV, IPEDS and accreditation regulatory-scope manifest — packaged as a signed, sequenced migration plan ready for execution.
Banner and Colleague are not stock packaged applications — they are 15-to-30-year-old customised SIS+ERP platforms with deep institutional fingerprints. A migration without an assessment is a guaranteed overrun.
Banner is the dominant SIS+ERP at large universities — Oracle DB-backed Java with deep PL/SQL customisation, Banner Self-Service JSP overrides, Banner Workflow business processes, Banner Document Management bindings and Banner ODS reporting layer. Colleague is the dominant SIS+ERP at community colleges and small private institutions — SQL Server-backed with Envision 4GL and UniData heritage, Colleague Web UI customisation, Colleague Reporting and a parallel customisation surface. Both platforms have been customised continuously for two or three decades by successive Registrars, Financial Aid Directors, Controllers and IT teams — and the operational knowledge of those customisations frequently leaves with the staff who built them.
An Ellucian Banner / Colleague migration assessment exists to turn that institutional fingerprint into a documented, regulatory-mapped, sized and priced execution plan before the migration starts. The assessment inventories every active Banner / Colleague module (Student, Finance, HR, Financial Aid, Advancement, Self-Service, Workflow, ODS / Reporting), catalogs every customisation (PL/SQL packages, JSP overrides, Workflow definitions, Document Management bindings, Envision customisations, Web UI overrides), maps every downstream integration (Canvas/Blackboard/D2L/Moodle, library, ID-card, housing, dining, parking, donor CRM, federal aid disbursement, student-employment payroll, IPEDS / NSC reporting) and produces a regulatory-scope manifest covering FERPA, Title IV, R2T4, IRS 1098-T, IPEDS, SACSCOC/HLC/NEASC/WSCUC/MSCHE/ACCJC, NC-SARA, VA GI Bill and Clery Act.
The Ellucian Banner / Colleague migration assessment also frames the strategic SIS decision explicitly. Most institutions keep Banner Student or Colleague Student as the SIS of record because Oracle Fusion Student and Workday Student lack full feature parity for complex course catalog, registration, degree audit and financial-aid integration — and instead move Banner / Colleague Finance and HR to Oracle Fusion Cloud or Workday Financials / HCM in a single fiscal-year cutover. The Ellucian Banner / Colleague migration assessment scores the SIS-stays / SIS-moves / full-Ellucian-Cloud options against the institution's R1/R2 profile, multi-campus complexity, customisation depth, course-catalog complexity, financial-aid complexity, accreditation continuity and IT staffing — and presents the recommendation with the evidence to defend it.
And why the assessment pays for itself in the first month of the migration by surfacing the surprises before they become budget overruns.
Fifteen-to-thirty years of in-house Banner PL/SQL or Colleague Envision customisations accreted across multiple Registrars accumulate quickly. The assessment surfaces every active package, every dead-but-loaded package, every legacy-only documentation artefact.
Point-to-point Banner Workflow handoffs, scheduled SQL Server export jobs, SFTP feeds to vendors, legacy ETL into the campus data warehouse, real-time integrations with Canvas/Blackboard/D2L/Moodle, ID-card and library systems.
Complex course catalog, multi-term registration, advanced degree audit, financial-aid integration. The assessment recommends SIS-stays vs SIS-moves with evidence the Provost can defend.
FERPA, Title IV, R2T4, IRS 1098-T, IPEDS, SACSCOC/HLC, NC-SARA, VA GI Bill, Clery Act — the assessment is often the first single regulatory-mapped manifest the institution has.
Title IV programme reviews can be triggered years post-disbursement. The assessment exposes evidence gaps in Banner / Colleague Financial Aid that need to be closed before any migration cutover.
Add/Drop, registration peaks, financial-aid disbursement, term-end grade posting, IPEDS submission deadlines, accreditation visits, NCAA compliance windows — the assessment sequences the migration around all of them.
A repeatable, evidence-based Ellucian Banner / Colleague migration assessment workflow sequenced to land before the next academic-calendar planning window without disrupting live Banner / Colleague operations.
Catalog every active Banner / Colleague module (Student, Finance, HR, Financial Aid, Advancement, Self-Service, Workflow, ODS / Reporting). Inventory every PL/SQL package, Envision customisation, JSP override, Workflow definition, Document Management binding. Classify live / dead / legacy-only.
Map every record class to FERPA, Title IV, R2T4, IRS 1098-T, IPEDS, SACSCOC/HLC/NEASC/WSCUC/MSCHE/ACCJC, NC-SARA, VA GI Bill, Clery Act. Registrar + Financial Aid Director + accreditation liaison + General Counsel co-sign the manifest.
Network-level discovery plus Banner Workflow / Colleague workflow catalog inspection. Document every integration (Canvas/Blackboard/D2L/Moodle, library, ID-card, housing, dining, parking, donor CRM, federal aid disbursement, IPEDS / NSC) with traffic profile and direction.
Score the SIS-stays-Banner / SIS-moves-to-Workday / full-Ellucian-Cloud options. Design the Oracle Fusion Cloud Finance/HCM or Workday Financials/HCM target. Map every Banner / Colleague domain to its target system.
Size each migration domain in person-weeks and infrastructure footprint. Price the execution as a fixed-fee SOW or T&M envelope. Sequence around academic-calendar windows — Add/Drop, registration peaks, disbursement, grade posting, IPEDS deadlines, accreditation visits.
Provost, CFO, CIO, Registrar, Financial Aid Director, Controller, AVP HR, VP Advancement, accreditation liaison, General Counsel, CISO sign the assessment plan. Execution kickoff the week after sign-off.
The signed assessment deliverable is the statement of work for the migration team and the evidence pack for the Board's audit committee.
Every active Banner / Colleague module catalogued with version, customisation density, usage profile, downstream-dependency count and migration-readiness score.
Every Banner PL/SQL package, Self-Service JSP override, Workflow definition, Document Management binding or Colleague Envision customisation and Web UI override — classified live / dead / legacy-only with successor-system implementation plan per live customisation.
Canvas/Blackboard/D2L/Moodle, library, ID-card, housing, dining, parking, donor CRM, federal aid disbursement, student-employment payroll, IPEDS / NSC — every integration with traffic profile, direction, latency budget and cutover sequencing.
FERPA, Title IV, R2T4, IRS 1098-T, IPEDS, SACSCOC/HLC/NEASC/WSCUC/MSCHE/ACCJC, NC-SARA, VA GI Bill, Clery Act — every record class with retention horizon, access regime and partitioning strategy. Co-signed by Registrar, Financial Aid Director, accreditation liaison, General Counsel.
Cutover windows sequenced around Add/Drop, registration peaks, disbursement, grade posting, IPEDS submission, accreditation visits, NCAA compliance windows, Title IX hearings. Critical-path Gantt chart per domain.
Per-domain person-weeks, infrastructure footprint, fixed-fee SOW or T&M envelope, contingency budget, risk-and-mitigation register. Signed by Provost, CFO, CIO and the Board's audit committee.
An Ellucian Banner / Colleague migration assessment is a structured, evidence-based readiness review of an institution's Banner or Colleague footprint before a major modernization — usually a move of Finance and HR off Banner / Colleague onto Oracle Fusion Cloud or Workday Financials / HCM, while typically keeping Banner Student or Colleague Student as the SIS of record. The Ellucian Banner / Colleague migration assessment produces: a complete module inventory (Banner Student, Banner Finance with FOAPAL chart of accounts, Banner HR, Banner Financial Aid, Banner Advancement, Banner Self-Service, Banner Workflow, Banner ODS, or the Colleague equivalents Finance, HR, Financial Aid, Advancement, Self-Service Web, Colleague Reporting); a customisation catalog (Banner PL/SQL customisations, Banner Self-Service JSP overrides, Banner Workflow definitions, Banner Document Management bindings, or Colleague Envision UI customisations and Web UI overrides); a downstream-integration map (Canvas/Blackboard/D2L/Moodle, library, ID-card, housing, dining, parking, donor CRM, IPEDS reporting, NSC reporting, federal aid disbursement); a regulatory-scope manifest (FERPA, Title IV, R2T4, IRS 1098-T, IPEDS, SACSCOC/HLC accreditation, NC-SARA, VA GI Bill, Clery Act); a sized-and-priced Ellucian Banner / Colleague migration assessment plan with academic-calendar-aligned timeline.
The Ellucian Banner / Colleague migration assessment is sponsored by the Provost (for academic-side modules) and the CFO (for finance/HR modules) jointly, with day-to-day ownership by the CIO. The accountable stakeholder map is well-defined in higher-ed: the Registrar owns Banner / Colleague Student scope including transcripts, course catalog, registration and degree audit; the Financial Aid Director owns Banner / Colleague Financial Aid including Title IV, R2T4, Pell, Stafford, Direct Loan and 1098-T; the Controller owns Banner / Colleague Finance including FOAPAL chart of accounts, AP, AR, cashiering, grants, fund accounting and GASB / FASB compliance; the AVP HR owns Banner / Colleague HR including position management, faculty load, payroll and benefits; the VP Advancement owns Banner / Colleague Advancement including donors, gifts, pledges and campaign attribution; the Title IX Coordinator and Dean of Students own conduct records; the accreditation liaison owns SACSCOC/HLC/NEASC evidence continuity; the Institutional Research / Effectiveness office owns IPEDS reporting and cohort analytics; the General Counsel owns FERPA and subpoena response; the CISO owns data security and FERPA technical safeguards.
A typical Ellucian Banner / Colleague migration assessment runs 6–10 weeks end to end, sequenced to land before the next academic-calendar planning window. Weeks 1–2 cover Banner / Colleague module inventory and customisation discovery — pulling the catalog of active Banner PL/SQL packages, Banner Self-Service JSP customisations, Banner Workflow definitions, Banner Document Management bindings, Colleague Envision UI customisations, Web UI overrides, Banner ODS / Colleague Reporting dependencies and the integration registry. Weeks 3–4 cover regulatory-scope mapping for FERPA, Title IV, R2T4, IRS 1098-T, IPEDS, SACSCOC/HLC/NEASC, state authorisation NC-SARA, VA GI Bill and Clery Act. Weeks 4–6 cover downstream-integration mapping including Canvas/Blackboard/D2L/Moodle, library, ID-card, housing, dining, parking, donor CRM, federal aid disbursement and student-employment payroll. Weeks 6–8 cover the migration-target architecture design (Oracle Fusion Cloud Finance/HCM, Workday Financials/HCM, or a hybrid). Weeks 8–10 cover the sized, priced, academic-calendar-aligned Ellucian Banner / Colleague migration assessment plan.
The Ellucian Banner / Colleague migration assessment uncovers a recurring set of surprises in higher-ed deployments. First: the Banner PL/SQL or Colleague Envision customisation footprint is typically 3–5× larger than the institution's current Banner / Colleague administrator team estimates — fifteen to thirty years of in-house customisations accreted across multiple Banner versions and multiple Registrars accumulate quickly. Second: the Banner Self-Service or Colleague Web UI customisation catalog includes student-facing pages that the institution had forgotten still exist — custom admissions workflows, scholarship-acceptance forms, holds-clearance pages, ADA accommodation requests. Third: the downstream-integration map regularly exposes 30–80 distinct integrations the institution wasn't tracking — point-to-point Banner Workflow handoffs, scheduled SQL Server export jobs, SFTP feeds to vendors, legacy ETL into a campus data warehouse, real-time integrations with Canvas/Blackboard/D2L. Fourth: the regulatory-scope map exposes records that are subject to FERPA, Title IV, R2T4, IRS 1098-T, IPEDS, SACSCOC/HLC, NC-SARA, VA GI Bill or Clery Act retention but are currently held without any retention-end-date governance — the Ellucian Banner / Colleague migration assessment is often the first time the institution has a single regulatory-mapped manifest.
Most higher-ed institutions keep Banner Student or Colleague Student as the SIS of record because neither Oracle Fusion Student nor Workday Student has full feature parity with Banner Student for complex course catalog, registration, degree audit, transcript and financial-aid integration — particularly at R1/R2 research universities and large state systems. The Ellucian Banner / Colleague migration assessment frames the decision explicitly: a 'Finance + HR off Banner / Colleague to Fusion or Workday, Student stays' pattern (most common, ~70% of institutions); a 'Finance + HR + Student all to Workday Student' pattern (growing, ~20%); a 'full Ellucian Cloud SaaS migration' pattern (about ~10%, typically smaller institutions). The Ellucian Banner / Colleague migration assessment scores each option against the institution's R1/R2 status, multi-campus complexity, Banner / Colleague customisation depth, course-catalog complexity, financial-aid complexity, accreditation evidence continuity and IT-staffing constraint.
Ellucian Banner / Colleague migration assessment fixed-fee pricing scales with institutional complexity. A small private 4-year college or community college running stock Colleague Finance + HR + Financial Aid with light customisation typically scopes to a $40K–$70K Ellucian Banner / Colleague migration assessment. A mid-size regional public university running Banner Student + Finance + HR + Financial Aid + Advancement with moderate customisation typically scopes to a $90K–$150K assessment. A large multi-campus state system or R1/R2 research university running every Banner module plus Banner Document Management, Banner Workflow, Banner ODS, complex Self-Service customisation, multiple downstream integrations and a 25,000+ FTE enrollment typically scopes to a $180K–$320K Ellucian Banner / Colleague migration assessment. Pricing is fixed-fee per institution scope; the deliverable is the sized, priced, regulatory-mapped, academic-calendar-aligned migration plan signed by Provost, CFO, CIO, Registrar, Financial Aid Director, accreditation liaison and General Counsel.
Yes — the Ellucian Banner / Colleague migration assessment is explicitly designed to run alongside live Banner / Colleague operations without touching the production tenant during peak academic-calendar windows. Discovery is read-only against a Banner ODS / Colleague Reporting replica or a snapshot of the operational data store; customisation cataloging works against Banner source control or Colleague Envision source where available, falling back to read-only file-system scans where source is not version-controlled; integration mapping uses network-level discovery and Banner Workflow / Colleague workflow catalog inspection; regulatory-scope mapping uses the Registrar's records-retention schedule, the Financial Aid Director's Title IV / R2T4 evidence inventory, the accreditation liaison's evidence binder and the IR/IE office's IPEDS query inventory. The Ellucian Banner / Colleague migration assessment is sequenced to avoid Add/Drop, registration peaks, financial-aid disbursement windows, term-end grade posting, IPEDS submission deadlines and accreditation visits.
The Ellucian Banner / Colleague migration assessment hands directly into the execution playbook. The sized, priced, regulatory-mapped, academic-calendar-aligned plan becomes the statement of work for the migration team. The Banner / Colleague module inventory drives the extraction job schedule. The customisation catalog drives the successor-system implementation backlog. The downstream-integration map drives the cutover sequencing — typically Banner Finance and HR move first (in a single fiscal-year cutover), Banner Student stays as SIS of record (or moves to Workday Student in a later wave), Banner Financial Aid stays through the Title IV / R2T4 evidence window. The regulatory-scope manifest drives the FERPA-partitioned archive design. The Provost, CFO, CIO, Registrar, Financial Aid Director, accreditation liaison and General Counsel sign the plan; execution starts the week after sign-off.
Book a 30-minute discovery call. We'll walk through your Banner / Colleague module footprint, your customisation density, your downstream-integration estimate, your FERPA, Title IV, IPEDS and accreditation obligations and your academic calendar — and give you a concrete Ellucian Banner / Colleague migration assessment scope, timeline and fixed-fee before the call ends.