Anthology Student consulting and development: An Anthology Student specialist who has done your staff’s jobs

An implementation is where the data comes across, the first integrations are wired up, and your staff decide whether to trust the new screens. The work that pays off is a migration rehearsed on a copy of your data, with a check-only run that lists what would change before anything does, and integrations built in your test environment in small steps, each with evidence. In my experience these projects fail on adoption more often than on code, so the people who will do the job see real output early, on real cases.

• Student data migration and conversion

  Rehearsed in test, safe to run again, and verified record by record before anyone signs off. The rehearsal is the first milestone, so you see real results on a copy of your data before you commit to a cutover date.

• Seven questions to ask before a student data migration

  Seven plain questions to put to anyone who is about to migrate your student data, and what a good answer sounds like.

• Both sides of the screen

  Why student system projects fail on adoption more often than on code, and what that changes about how the work is done.

A stable instance usually has a spreadsheet beside it: a report that does not quite match the screen, a routine step someone retypes each term, a workflow nobody dares to touch. Each workaround is a staff member telling you what the system does not do for them, and the product can usually do it. Find out what is already automated before adding anything new, then start with the one process that causes the most rework each term.

• A report that documents every workflow you are running

  A self-service report that lists, classifies and explains every production workflow, read from the system itself, so nobody has to remember what is running.

• Workflow and forms automation

  Workflows and forms that do the routine steps inside the system your staff already work in, and a ten-question self-check of your own workflow estate.

• Higher-education reporting and analytics

  SSRS reports and Power BI dashboards that reconcile to the screens your staff already trust, with the exceptions at the top.

CampusNexus Student is an earlier name for the same product line as Anthology Student, and I have worked on it under each of its names since 2007, including administering the product and its SQL Server databases across a multi-campus institution. A school still running it on its own servers needs the same first step as any other: a current list of every integration, custom report and workflow, with an owner for each, because any upgrade, audit or data migration starts with that list. Keep a test copy that matches production, and get the vendor’s answers in writing before you decide anything.

• CampusVue, CampusNexus, Anthology Student: three names, one product line and a new owner

  The three names with sources, who has owned the product since the end of 2025, and five low-risk steps for a school running it now.

• A report that documents every workflow you are running

  The inventory step, done by making the system describe itself: every production workflow, classified and documented in a report staff run for themselves.

• Student data migration and conversion

  If the next step is a move, this is how a migration is rehearsed on a copy of your data, made safe to run twice, and verified record by record.

Ellucian has owned the product since the end of 2025 and says that support, service and contract terms continue, and that integrations, APIs and customizations keep working; its page for Anthology customers gives no product roadmap, and I will not guess at one. The steps that do not depend on what any vendor does next are an inventory of every integration, report and workflow, your customizations written down, and direct questions to your account contact with the replies kept. I am independent of the vendor, I have not worked on Banner or Colleague, and I say so on the first call.

• What changed with the new owner, and what did not

  What is publicly known about the sale to Ellucian, with sources, what Ellucian has said in writing, and what it has not said.

• Which student information systems do you work with?

  Mostly Anthology Student, now an Ellucian product, and not Banner or Colleague. The integration, reporting and migration methods carry across student systems; the product knowledge is what saves you time.

• Seven questions to ask before a student data migration

  If the weighing ends in a move, the seven questions to put to any vendor before your student data is migrated, and what a good answer sounds like.