Production-grade ellucian banner / colleague data archival. FERPA-indefinite transcript retention, GASB/FASB/IPEDS regeneration, sub-second registrar lookup, tiered storage. Cut retention TCO 70–85% by retiring Banner Oracle and Colleague SQL Server without losing a single transcript or audit-evidence row.
Most higher-ed institutions don't keep Banner or Colleague running after migration because they love the legacy UI. They keep it running because FERPA requires indefinite transcript retention and they have no other way to satisfy alumni transcript requests. That is exactly the problem ellucian data archival solves.
Higher-ed retention obligations span the longest horizons of any commercial sector: FERPA-driven indefinite transcript retention (a 1955 alumnus may still order a transcript), Title IV federal financial aid retention (5 years post-award + extensions), IRS 1098-T retention (4 years + reissue capability), DOE program review records (3 years + extensions), state public-records laws (varies, often 7–30 years for fiscal records at public universities), NACUBO endowment audit trails (indefinite for permanently restricted), sponsored-programs federal indirect-rate audit (3 years post-final-report). After a finance/HR migration to Fusion, every one of these obligations still rests on the historical Banner or Colleague data — not on Fusion.
The traditional response is to keep Banner Oracle or Colleague SQL Server running in read-only mode 'for archive purposes'. That works, but costs $400K–$900K/year per mid-sized university in licence, infra, DBA time and security overhead — to serve a few hundred transcript requests per month and a handful of audit drills per year. The economics get worse as Ellucian raises licence fees on a smaller and smaller install base of read-only customers.
Syntra ETL's ellucian banner / colleague data archival product is the modern replacement: extract every retention-relevant table once, write to immutable cloud object storage with hash-signed evidence, build the registrar transcript-lookup UI and alumni self-service portal, satisfy every retention rule for 70–85% less. The source Banner Oracle or Colleague SQL Server database can be fully decommissioned (or kept in cold standby for emergency-only access).
Each one a line item on the post-migration TCO model.
Banner Oracle Database EE licence + Colleague SQL Server EE licence run $150K–$400K/year combined. Archive cloud-object storage costs a small fraction. Direct retirement saves six figures annually.
Banner production servers refresh every 4–5 years at $200K–$500K per cycle. After archival, no refresh needed — cloud object storage scales infinitely without capex.
Banner DBA + Colleague DBA combined typically 1.5–2.5 FTE. Archive operations need a fraction of that — small ops team monitoring storage and serving registrar requests.
Quarterly Oracle CPU patching, Banner upgrade cycles, security review of a 17,000-table legacy schema — all gone. Cloud object storage carries its own security model.
Banner DR drills cost $100K+ per year in infra and time. Cloud-native archive replicates across regions automatically — DR is built in.
Banner transcript-request lookup typically takes 5–30 seconds. Indexed archive lookup runs sub-second — registrar service quality goes up while cost goes down.
A repeatable, governed workflow built around higher-ed's unique retention obligations. Typical timeline: 4–7 months.
Per-data-class retention rule defined and signed off: FERPA-indefinite for SHRTRCE/ACAD.CRED, Title IV-5yr for FA awards, IRS-7yr for AP/payroll, state-specific for public-records-act exposure, GASB/FASB-historical for finance journals, donor-indefinite for permanently restricted endowment provenance.
Cloud object storage configured (S3/GCS/Azure Blob) with immutability locks (S3 Object Lock, etc.), KMS key hierarchy, tiered storage policies (hot/warm/cold), access logging to SIEM, registrar lookup-service architecture, alumni transcript-portal design. IT security review and approval.
Native Banner Oracle and Colleague SQL Server extractors pull every retention-relevant table. Output written as Parquet to cloud object storage, hash-signed at extraction with SHA-256 evidence, indexed for fast lookup. Transcript records routed to immutable-tier storage separately.
Transcript-lookup UI built for registrar back-office staff with FERPA-compliant access controls. Alumni self-service portal launched (or integrated with National Student Clearinghouse). Programmatic API exposed for Parchment/Credentials Inc/JST integration.
Registrar acceptance testing on real transcript requests, audit-evidence regeneration tested against historical GASB/IPEDS submissions, alumni portal pilot rollout. Banner Oracle / Colleague SQL Server placed in read-only mode (then decommissioned outright once the archive has served 3–6 months of production traffic).
The full higher-ed retention map, with hash-signed evidence on every row.
SHRTRCE/ACAD.CRED with full referential context (course catalog, instructor, term, grade), immutable storage, sub-second indexed lookup, FERPA access-audit logging on every read.
FGBJVCD journals, FAR*/AP invoices, FOR*/AR receivables, FZR* sponsored programs — retained for 7+ years IRS, indefinite for historical comparability, GASB/FASB statement regeneration on demand.
PHPCALC payroll, PEBBNFC benefits, NBRPOSN positions — retained per FLSA (3yr), IRS (4yr), ERISA (6yr), state wage laws (often 7yr), with original tax-form regeneration capability.
APRSPRR donors, AGAGIFT gifts, APBPLDG pledges, ASBPGRP planned giving — retained indefinitely for permanently restricted endowment provenance, donor-intent enforcement, planned-giving fulfillment.
FZR* awards with full effort-allocation, indirect-rate base, federal report-deliverable trail — retained 3 years post-final report per OMB Uniform Guidance, longer for NIH/NSF audits.
RPRAWRD award records, COD originations, Title IV disbursements — retained 5+ years per DOE program-integrity rules, queryable for program-review defense.
Ellucian banner / colleague data archival is the practice of moving historical Banner and Colleague data — closed fiscal years of Finance journals, retired employee HR records, fulfilled donor pledges, completed financial-aid awards, and crucially the indefinite transcript file — out of the live production database into a queryable long-term store, while keeping the data fully retrievable for FERPA registrar requests, IRS audits, Department of Education program reviews, NACUBO endowment audits and IPEDS reporting. The point is to retire the burden of running a Banner Oracle or Colleague SQL Server production database purely to satisfy retention rules. Syntra ETL's ellucian-banner-colleague data archival product keeps SHRTRCE/ACAD.CRED transcripts available indefinitely, AP/AR/GL queryable for the statutory windows, and donor history accessible — all without the licence and infra cost of a live source system.
Migration moves data into Fusion (or another live target) and the source-system data is no longer the system of record. Archival moves data into a long-term retention store where it remains the historical system of record — readable forever (for FERPA transcripts) or for the statutory window (typically 7 years for IRS, 5 years for Title IV, 3 years for IPEDS detail), without being editable. Most institutions need both: migration for the operational years (current + prior FY) that move to Fusion, archival for the older history that doesn't need to be live in Fusion but must remain retrievable when alumni request transcripts, when IRS audits a 1098-T from 6 years ago, or when DOE conducts a program review of historical Title IV awards.
Everything that carries a retention obligation. Banner: FOAPAL Finance history (FGBJVCD journals, FAR* AP, FOR* AR, FZR* sponsored programs), HR/Payroll history (PHPCALC payroll, PEBBNFC benefits), Advancement history (AGAGIFT gifts, APBPLDG pledges), Financial Aid history (RPRAWRD awards, COD records), Student records (SHRTRCE transcripts retained indefinitely under FERPA, SARADAP admissions, SHRGRDE grades, registration history). Colleague: GLA/AP/AR Finance history, payroll history, advancement, ACAD.CRED transcripts. All retained with hash-signed evidence, indexed for sub-second lookup, and tiered for cost (hot for recent + frequently accessed, warm for medium-age, cold/Glacier for ancient).
FERPA (Family Educational Rights and Privacy Act) does not specify a maximum transcript retention period, and most US state retention schedules require indefinite retention — explicitly so a 70-year-old alumnus can still order a transcript from their 1975 enrollment. Syntra ETL's ellucian data archival product treats transcripts as the longest-retention data class: SHRTRCE/ACAD.CRED rows are extracted with full referential context (course catalog, instructor, term, grade), hash-signed, written to immutable cloud object storage (S3 Object Lock or equivalent), and indexed in a fast lookup table keyed by SPRIDEN_PIDM (Banner) or PERSON.ID (Colleague) so a registrar can retrieve any transcript in under a second. Every access is logged to a FERPA audit trail. No source database needed to satisfy the indefinite retention obligation.
Yes — that's the whole point. After the source Banner Oracle or Colleague SQL Server database is decommissioned, the archive continues serving transcript requests through three access paths: a self-service alumni transcript-request portal where authenticated alumni order their own transcripts (integrated with National Student Clearinghouse or institution-branded), a registrar back-office UI for staff handling complex cases (consolidating transcripts across name changes, fixing historical errors per FERPA correction procedures), and a programmatic API for integration with Parchment, Credentials Inc, Joint Services Transcript and other transcript-delivery vendors. Service-level agreements typically commit to sub-second response on the indexed transcript record.
Significant. A typical mid-sized university running Banner for read-only post-migration retention spends $400K–$900K/year on: Oracle Database licence ($150K–$400K), Banner Forms / SSB licence renewal ($100K–$200K), Oracle hardware refresh amortization, DBA staff time keeping it patched and secured, and the inevitable disaster-recovery infra. A Syntra ETL ellucian-banner-colleague archive serving the same retention obligation typically runs $40K–$120K/year all-in: cloud object storage (S3 Glacier for cold, S3 IA for warm, S3 Standard for hot), Parquet query compute (Athena/Trino, pay-per-query), the indexed transcript-lookup service. Most institutions achieve 70–85% TCO reduction in year one.
An ellucian banner / colleague data archival project is faster than a full migration because there's no Fusion target to align with — the archive is the target. Typical timeline: 4–7 months from kickoff to full transcript archive live and source Banner/Colleague placed in read-only mode (or decommissioned outright). Phase 1 (1–2 months): scope, retention rule definition per data class, archive design and IT security review. Phase 2 (2–3 months): bulk extract of all historical Banner/Colleague tables, write to immutable cloud storage with hash-signed evidence, build the transcript-lookup index and registrar UI. Phase 3 (1–2 months): registrar acceptance testing on real transcript requests, alumni portal launch, source-system read-only mode.
Higher-ed financial reporting (GASB for public universities, FASB for private) requires historical comparability across multiple fiscal years; IPEDS (Integrated Postsecondary Education Data System) requires annual federal data submission. Syntra ETL's ellucian data archival product preserves the full FOAPAL/CF chart context — fund classification, restricted/unrestricted net asset designation, sponsored-programs indirect-rate calculations — so historical GASB/FASB statements can be regenerated from the archive at any time. IPEDS Finance, Human Resources, Fall Enrollment, 12-Month Enrollment and Graduation Rate surveys can be regenerated from archived data on demand. Reporting continuity is preserved without keeping Banner/Colleague running.
30-minute call. We'll walk through your Banner/Colleague footprint, FERPA transcript volume, retention obligations, registrar workflow and TCO baseline — and give you a concrete ellucian banner / colleague data archival plan with cost model.