Back to Resources

Migration Hub

Enrollment Manager Migration Hub for VASCOs

The VA-ONCE to Enrollment Manager migration hub for VASCOs. Practical context, pre-cutover checklists, and pitfalls to watch for, curated for the School Certifying Officials who have to keep certifications flowing on both sides of the switch.

Why this page exists

VA-ONCE has been the default certification system for a generation of VASCOs. The VA is retiring it and consolidating enrollment certification into Enrollment Manager. Most of the skills and habits VASCOs have built transfer over, but the mechanics, field layouts, and a few validation rules do not. This page collects the guidance we wish had existed when our own institutions started planning cutover: what is changing, what to do before the switch, where people tend to get tripped up, and which of our existing articles apply to the new workflow.

What is changing

VA-ONCE is sunsetting

The legacy VA-ONCE portal is being retired in favor of Enrollment Manager, which brings certifications, amendments, and reporting under a unified web application. Institutions are migrated on a rolling basis, so your cutover date may differ from a peer school, even inside the same state system.

Enrollment Manager at a glance

Enrollment Manager is the VA Online Certification of Enrollment application. It is browser-based, role-scoped through the VA's Education Liaison Representatives (ELRs), and is where you submit initial certifications, amendments, and last-date-of- attendance updates. Reporting and search live inside the same interface, so batch operations that used to span multiple screens now happen in one place.

What is different from a VASCO's perspective

  • •Field layout and labels: many VA-ONCE fields have moved, renamed, or split. Muscle memory built over years of VA-ONCE data entry is the first thing to audit.
  • •Validation is stricter up front: Enrollment Manager catches more issues at submission time. That is a good thing, but it means some workflows that used to “submit now, fix later” no longer work.
  • •Access provisioning runs through ELRs: your VA-ONCE login does not automatically become an Enrollment Manager login. New users and role changes must be requested explicitly.
  • •Chronological ordering matters more: out-of-order amendments that VA-ONCE would quietly accept can be rejected or routed for manual review.
  • •SIS integrations need revalidation: if your Student Information System exports CSVs for ingestion, formats and required columns need to be re-checked against Enrollment Manager's expectations.

Pre-cutover migration checklist

Work this list before your institution's published cutover date. Every item is something a VASCO can start on independently, without waiting for IT or the registrar.

  1. Audit open certifications in VA-ONCE

    Pull a list of every certification that is still pending, amended, or in error-resolution status. Resolve anything that can be resolved before cutover, so you do not carry ambiguous state into the new system.

  2. Document your custom workflows

    Write down every “we always do it this way” rule for Yellow Ribbon students, VR&E (Chapter 31) approvals, compressed terms, study abroad, and dual-enrollment cases. If it lives only in your head, assume it will disappear the first week on Enrollment Manager.

  3. Verify user access provisioning

    Confirm every VASCO on your team has the right Enrollment Manager role assigned through your ELR. Include backups and cross-trained staff. Access requests take longer than people expect, so do this weeks in advance.

  4. Confirm training is complete

    Work through the VA-provided Enrollment Manager modules, then do a dry run on sample data if your ELR or region offers a sandbox. Keep a note of any screens or validations that surprised you, so your team can plan around them.

  5. Update your internal SOPs and checklists

    Any SOP, checklist, or onboarding document that references VA-ONCE screens needs a second version for Enrollment Manager. Date-stamp both, so your team can see which applies based on cutover status.

  6. Revalidate SIS exports and imports

    Export a sample CSV from Banner, PeopleSoft, Workday, or whatever your SIS is, and compare column-by-column against Enrollment Manager's expected format. Catch shape mismatches in a sandbox, not during peak certification season.

  7. Brief your registrar, bursar, and ELR contacts

    Make sure the people upstream and downstream of you know the cutover date, who the backup VASCOs are, and what to do if a student reports a payment issue during the transition window.

Common pitfalls to watch for

BLUF (Bottom Line Up Front): The single highest-leverage habit is strict chronological ordering of certifications and amendments. If you submit an amendment that covers a date range earlier than an already-submitted certification, Enrollment Manager is far less forgiving than VA-ONCE was. Sort by effective date, submit in order, and keep a paper trail.

Watch for: out-of-order amendments

What happens: an amendment filed for an earlier term is blocked or routed to manual review because a later term was already certified.

What to do: before cutover, sort your backlog by effective date and resolve amendments oldest-first. After cutover, adopt chronological order as a standing rule, not an exception.

Watch for: carried-over data that did not migrate cleanly

What happens: notes, custom fields, and non-standard free-text entries from VA-ONCE may land in Enrollment Manager truncated, blank, or in the wrong field.

What to do: spot-check a representative sample of migrated records in the first week. Focus on Yellow Ribbon and VR&E files, which have the most non-standard annotations.

Watch for: training time recalculations

What happens: rounding differences between VA-ONCE-era training time and Enrollment Manager's calculation can flip a student's status across a threshold, which in turn changes Monthly Housing Allowance.

What to do: recompute training time for active students during cutover and flag any that cross a half-time, three-quarter-time, or full-time line for review.

Watch for: silent access gaps on backup VASCOs

What happens: the primary VASCO is provisioned, but backups or cross-trained staff were not migrated. The first time a backup needs to certify, they are locked out.

What to do: have every named backup log in and perform a no-op search inside Enrollment Manager during the first week. If they cannot, route an access request through your ELR immediately.

Watch for: SIS export schema drift

What happens: the CSV that cleanly ingested into VA-ONCE-adjacent tools fails validation against Enrollment Manager, often because of date formats, program codes, or new required columns.

What to do: treat your SIS export as a contract. Test it against Enrollment Manager before a live certification run, and keep a diff of any column changes your IT team made during the project.

Related resources

Deep-dive guides from the VASCO Assistant knowledge base that complement this hub.

Where VASCO Assistant fits

VASCO Assistant is the offline translation and verification layer between your university's SIS and Enrollment Manager. It normalizes exports, flags the chronological and training-time issues called out above, and gives your team a checklist-backed path from SIS data to a clean Enrollment Manager submission.

Everything runs locally, so student PII stays on your machine. If that sounds useful for your institution's cutover, the best next step is the waitlist or a direct conversation with our founder.

Working through a cutover?

Join the early-access waitlist to hear when VASCO Assistant launches, or message our founder on LinkedIn to talk through your institution's migration plan.

Join the waitlist

Prefer a direct conversation? Message Blason Taon on LinkedIn.