Before moving to Ellucian Student: map the interfaces that must keep working

Write down which Student functions will move in this phase and which systems will stay. For the Banner path, Ellucian uses the name Ellucian Student powered by Banner. Confirm the contracted target, deployment, modules and release with Ellucian. A SaaS implementation, managed hosting and an on-premises upgrade can change different responsibilities.

Give each transfer a stable ID in a working register. Link that ID to its current specification, staff contact and proposed replacement. The purpose at this stage is to find the work and decide its sequence; detailed interface acceptance tests come after the team confirms the design.

Bring the scheduler administrator, integration lead and department system owners together. Compare scheduled jobs, file-transfer logs, existing specifications and staff instructions. Have departments identify downloads, spreadsheets, shared folders and manual uploads they use to complete a task. Review enough of the academic and financial calendars to include infrequent work such as term setup and annual reporting.

Follow each transfer to the person or process that uses it. Record any intermediate script, mapping file or staff step. Two job names may describe stages of the same transfer; one job may also supply several recipients. Keep those relationships rather than counting names as separate interfaces.

UNCG's SaaS planning page asks departments to identify daily processes, reports, data needs and connections to other systems. Its page describes October 20–22, 2026 planning sessions and does not establish a completed migration. That is a useful prompt to involve staff beyond the integration team.

For each direction of transfer, identify the source that is authorized to supply the information, the receiving system and the task it supports. Separate a one-time conversion load from recurring updates. Record the business deadline, including the time zone and any earlier job that must finish first.

Use precise descriptions. 'Connected to Banner' does not say whether a system receives a nightly file, sends approved changes back or waits for a staff upload.

Mississippi State's March 23, 2026 project-management software RFP Q&A makes this distinction: question 3 discusses an export for import into AiM, while question 5 describes information flowing from Jaggaer into the proposed project system. This is a dated procurement clarification, not a Student interface specification or a claim about a delivered implementation.

Use the checks below to complete your own register. Add the transfer ID, status, named employee, next action and due date to each internal row.

Ask Ellucian and the receiving vendor to review the actual transfer requirement against the contracted target. Where Ethos Integration is proposed, obtain confirmation of the required resource, version, fields and operations in your environment. Keep an unanswered requirement open; a named connector alone is insufficient.

Identify who must build or change each part, including institutional scripts and the receiving application. Confirm access approvals and a usable test arrangement early. Mississippi State's question 8, for example, said a Bluebeam Studio sandbox would not be provided for that procurement. It illustrates why the project plan should record test constraints instead of assuming every supplier can provide the same environment.

Do not assume a current direct database query, local directory or script can move unchanged. Request a supported target method and the work needed to replace it. This guide does not prescribe product commands or authorize changes to production transfers.

Have the integration lead and affected departments place each transfer in one of the groups below. Record the reason and the conditions for changing that decision. Before leaving a transfer in place, have both system owners confirm it can still run during the phase and that staff will receive the records they need.

Illustrative example: Student sends a registration file to an intermediate process that supplies the learning platform. The learning-platform job depends on that intermediate file, so changing only the first transfer could break the later step. Map both, name the staff who maintain the mapping, and agree how the full chain will switch or continue during the transition.

A separately approved AI tool could compare redacted transfer descriptions with approved vendor responses and draft a list of missing answers. Supply transfer IDs and source-document references. Exclude credentials, student records and restricted infrastructure details unless their use has been expressly approved.

Ask it to identify a requirement with no matching answer and cite both records where it finds a possible conflict. Have the integration lead check every flag against the original documents before assigning a question to a vendor. Reject inferred support claims. The lead decides which questions remain open; AI does not approve a method, change a mapping or set the cutover sequence.

This is a proposed external drafting method, not a native Ellucian feature. Keep record counts and financial comparisons in approved queries or calculation tools.

Bring the sponsor the transfers that block the first phase, the decisions still required and the work assigned to each team. The schedule should allow time for vendor answers, implementation, testing and department review.

After staff accept a replacement, the cutover lead should confirm that every known recipient has switched and that no scheduled or manual task still needs the old transfer. Retire it through the institution's change process, retaining the required specifications and results.

Altioras Global's Ethos & Integration Modernization service can help trace these transfers with staff and prepare the sequence of changes for the institution to approve.