Pre-built ellucian-banner-colleague data conversion for Finance, HR/Payroll, Advancement and Financial Aid. Banner Oracle and Colleague SQL Server native extractors, FOAPAL/CF to Fusion COA crosswalks, FBDI/HDL emitters, FERPA transcript archive routing, row-level reconciliation. Audit-ready evidence at every load.
The hard part isn't pulling rows from Oracle or SQL Server. It's translating Banner's FOAPAL string and Colleague's CF segment model into Fusion's six-segment COA without losing higher-ed fund-accounting context, sponsored-programs traceability or FERPA-grade transcript fidelity.
Ellucian Banner runs on Oracle Database with a vast schema: SATURN/SPRIDEN holds the person master, FGBACTV holds the active FOAPAL combinations, FGBJVCD holds journal vouchers, FAR* holds AP, FOR* holds AR, FZR* holds sponsored programs, NBRPOSN holds positions, SHRTRCE holds transcripts, APRSPRR holds donors. Colleague runs on SQL Server (formerly UniData) with a UniBasic legacy wrapper: PERSON, STAFF, GLA, ACAD.CRED files accessed through ENVISION. Oracle Fusion ERP uses a different shape — Journals tied to a six-segment COA, AP Invoices tied to Suppliers and Liability accounts, HCM Positions tied to a global business-unit model.
Every ellucian banner / colleague data migration to Oracle Fusion has to bridge those gaps without breaking the higher-ed audit chain that links a GL journal line back to its originating student account, sponsored-program award, donor pledge or faculty position. Custom PL/SQL and T-SQL extracts plus one-off transformation packages can do it — but every domain becomes a multi-month negotiation between Finance, Sponsored Programs, Advancement, HR, Registrar and IT. Syntra ETL replaces that with pre-built crosswalks refined across dozens of Banner and Colleague conversions.
The same engine handles three deployment scenarios: Finance + HR + Advancement migration with Banner/Colleague Student kept on Ellucian (the Campus Solutions–style hybrid pattern adopted by the vast majority of universities), full big-bang including Student in the same wave (rare, typically only at smaller institutions), or the phased pattern where Advancement leads, Finance follows in fiscal-year wave two and HR/Payroll lands in wave three.
The transformations Syntra ETL ships pre-built. No custom PL/SQL or T-SQL scaffolding, no multi-month bespoke conversion development.
Banner FOAPAL combinations walked from FGBACTV, classified by reporting materiality, collapsed to Fusion COA segments. Same engine handles Colleague CF chart. Low-volume codes retired in cleanup.
Restricted, unrestricted, temporarily restricted, permanently restricted net asset classifications preserved through chart redesign. Endowment principal-vs-income separation maintained for GASB/FASB reporting.
Banner APRSPRR donor master de-duplicated across decades of accumulated alternate-spelling, married-name and address-change records. Gift/pledge history consolidated under canonical donor IDs.
Banner FZR* sponsored-programs records mapped to Fusion Project segments with award/budget/expense traceability preserved for federal indirect-rate audits and NIH/NSF reporting.
Banner NBRPOSN positions plus SIRASGN faculty-load per-term assignments converted to Fusion HCM positions with effort allocation across teaching/research/administrative cost-centers preserved.
SHRTRCE (Banner) and ACAD.CRED (Colleague) transcripts routed to FERPA-indefinite archive separately from operational data. Sub-second registrar lookup; immutable signed evidence on every read.
A repeatable load order that respects Fusion ERP/HCM data dependencies. Skip a step and your journal load fails on missing accounts or suppliers.
Fusion enterprise structures, ledgers, BUs, COA segments, accounting calendars, payment terms, payment methods, tax setup, position structures configured. Loaded via FSM tasks — not user-facing data, but everything downstream depends on it.
Vendors (FBDI Supplier Import from Banner FTVVEND), customers (FBDI Customer Import from FTVCUST), workers (HDL Worker.dat from PEBEMPL), positions (HDL Position.dat from NBRPOSN), donor master (Fusion Advancement equivalent from APRSPRR). Loaded in dependency order.
Open AP invoices (FBDI), open AR receivables (FBDI), open POs (FBDI), open requisitions, open sponsored-programs awards (FBDI Project Resource), open pledge schedules. Migrated with full approval-state context preserved through AMX flows.
Period-end balances from FGITRND historical trial balance loaded as opening balances per fund per natural-account per period. Detail journals loaded for the operational reporting window (typically current FY + prior FY). Older history routed to long-term archive.
PHPCALC payroll history, PEBBNFC benefits history, SIRASGN faculty-load history loaded via HDL bundles. Statutory retention windows preserved. Union-contract and bargaining-unit data preserved for grievance defense.
Final delta replay via CDC, parallel-month reconciliation, sign-off pack (trial balance, AP aging, AR aging, payroll register, donor reconciliation — Banner/Colleague vs Fusion to the cent). Production cut to Fusion. Hybrid SIS layer live.
Every ellucian banner / colleague data migration load produces signed drill-downable reconciliation reports.
Source Banner/Colleague row count vs Fusion-loaded row count per business unit per fund per period. Variance threshold zero. Domain-by-domain (journals, AP, AR, positions, donors, transcripts).
Per-Fund per-period GL debit/credit sums reconciled, AP outstanding per vendor reconciled, AR aging buckets reconciled. Variance flags surface before any subsequent load is allowed.
Each record content-hashed at Banner/Colleague source and re-hashed post-Fusion-load. Hash drift indicates transformation bug or corruption — surfaced with row-level diff.
Banner FGITRND trial balance per period per Fund vs Fusion GL trial balance, drillable to journal line, sub-ledger source and originating Banner FOAPAL string.
FZR* award balances, encumbrances and expense totals reconciled per award per period for federal NIH/NSF/DOD reporting and indirect-rate audit defense.
SHRTRCE/ACAD.CRED row counts and content-hash signatures reconciled between source and FERPA archive. Spot-check sampling validates transcript integrity post-load.
Ellucian banner / colleague data migration is the process of moving Finance (FOAPAL or CF chart, GL journals, AP invoices, AR receivables, budget, fixed assets, endowment, sponsored programs), HR/Payroll (position control, benefits, time entry, faculty load), Advancement (donor, gift, pledge, campaign), Financial Aid (FA award, COD, Title IV) and selected Student records (transcripts for FERPA archive) from a Banner Oracle database or Colleague SQL Server database into Oracle Fusion ERP, HCM and (optionally) a long-term archive. The technical heart is two-fold: direct database extraction through native Oracle and SQL Server connections (Banner is Oracle-native, Colleague is SQL Server with UniBasic legacy wrappers), and Oracle-validated FBDI/HDL emission with full higher-ed-specific FOAPAL/CF chart translation.
Migration is the end-to-end project (extract + transform + load + reconcile + cutover); conversion is the transformation layer specifically. Syntra ETL's ellucian-banner-colleague data conversion engine ships pre-built rules for FOAPAL-to-Fusion-COA collapse (Fund/Org/Account/Program/Activity/Location to Fusion's six-segment chart), CF-to-COA collapse for Colleague, position-control to Fusion HCM position mapping, GASB fund-accounting preservation, sponsored-programs FZR* to Fusion Projects routing, donor-record consolidation, and FERPA-grade transcript archiving. These are rules that on an SI-led project would otherwise eat 8–14 months of bespoke PL/SQL and T-SQL development.
Banner's FOAPAL (Fund-Organization-Account-Program-Activity-Location) is a six-element string driving every financial transaction; Colleague's CF (Component Filter) plays the analogous role. Neither maps cleanly to commercial six-segment COAs. Syntra ETL's ellucian-banner-colleague data migration tool walks FGBACTV (Banner active code combinations) and Colleague GLA, identifies actual material usage (codes carrying >$10k aggregate vs codes used once in 2009), and proposes a Fusion COA design: Fund segment carries Banner Fund, Cost-Center segment carries Banner Organization, Natural-Account carries Banner Account, Project segment carries Banner Activity, Program segment carries Banner Program, Location segment carries Banner Location. Sponsored Programs (FZR*) route to Fusion Project segments. The crosswalk is signed off by Finance, Sponsored Programs and Advancement before any production load.
Yes. Banner NBRPOSN (position) and NBRBJOB (position class) records, plus the salary-encumbrance accounting that links positions to FOAPAL, are converted to Fusion HCM positions with full position-history preservation. Colleague's POSITION file plays the same role. Faculty Load assignments (SIRASGN) preserve the per-term faculty-to-course assignments with course-level effort calculation that Banner uses for payroll allocation across teaching vs research vs administrative cost centers. Union contract terms, bargaining-unit assignments, longevity step tables and tenure-track milestones all carry through to Fusion HCM equivalents with full effective-dated history.
Syntra ETL emits Fusion-native load formats for every ellucian-banner-colleague data domain: FBDI Journal Import for GL journals (with FOAPAL→COA collapsed), FBDI AP Invoice Import for Banner FAR* AP records and Colleague AP, FBDI AR Receipt Import, FBDI Supplier Import for vendor master, FBDI Project Resource Import for sponsored programs, FBDI Asset Mass Additions for Banner FFB* fixed assets; HCM Data Loader (HDL) for workers, positions, benefits, payroll history; and REST API payloads for incremental delta loads during parallel-run and post-cutover. Every payload is validated against the current Oracle Fusion 26x release schema before submission, so validation errors surface locally — not in a 6-hour Fusion ESS job that fails on row 122,000.
Every record extracted from Banner or Colleague is hashed at the source (header hash + line hashes + reference-data fingerprint). Every record loaded into Fusion is re-hashed post-load. The reconciliation engine compares counts (journals, AP invoices, AR receipts, positions, donors, transcripts), sum totals (GL debit/credit per Fund per period, AP outstanding per vendor, AR aging per period) and hash signatures per business unit per period. Any record that fails Fusion validation is captured with the exact field-level reason ready for bulk fix. Output is a signed timestamped reconciliation pack: Banner FGITRND trial balance vs Fusion GL trial balance to the cent, AP outstanding vs outstanding, AR aging vs aging, payroll register vs register. Internal audit signs off on the pack directly.
Yes. After the initial bulk load, Syntra ETL captures Banner/Colleague deltas via Oracle CDC (LogMiner/GoldenGate-style) or SQL Server CDC and replays them into Fusion through REST APIs. This supports the standard parallel-run pattern: Banner/Colleague Finance continues taking transactions for 1–2 month-end cycles while Fusion Finance is validated to the cent. Once Finance, Sponsored Programs, Advancement and Internal Audit sign off, new transactions cut to Fusion and the Banner/Colleague Finance module moves to read-only archive mode. The Student SIS layer (Banner Student or Colleague Student) typically continues uninterrupted through the governed hybrid integration layer, with no parallel-run required on the student side.
FERPA requires indefinite retention of academic transcripts plus auditable access logs on every transcript read; Title IV (US Department of Education financial aid) requires 5+ years post-award retention; IRS 1098-T tuition statements require 4-year retention plus reissue capability. Syntra ETL's ellucian data migration preserves the full chain: GL line in Fusion → AP invoice → Banner FOAPAL coding → originating Student account, with every hop signed and timestamped. SHRTRCE/ACAD.CRED transcript rows land in the FERPA-indefinite archive with sub-second registrar lookup. Title IV award records and 1098-T detail land in the compliance archive with statutory retention enforced. No reconstruction needed when DOE audit, IRS audit or state higher-ed audit arrives.
30-minute call. Walk through your Banner/Colleague volumes, FOAPAL/CF chart design, sponsored-programs scope, transcript depth and hybrid SIS strategy — leave with a concrete ellucian banner / colleague data migration plan.