Advant-led
Advant leads the implementation work, with your team supplying institutional knowledge and making the decisions.
Your team reviews, tests and approves.
Implementation & migration
Admissions software.
Plan your migration.
Plan your move to Crossroads around your admissions cycle. Agree what needs to move, how your team will test it and who owns each step, from data preparation to staff readiness.
Start with your process
A plan your people
can work from.
A change of admissions software involves more than configuration. Work through the application paths, campus differences, data and responsibilities together, with decisions your team can review.
- 01 / Discover
Map your process.
Agree the applications, campuses and workflows in scope. Identify the decisions that belong to admissions, the systems that need to connect and the people who will approve the result.
- 02 / Prepare
Prepare and migrate your data.
Define what needs to move, how source information maps to Crossroads and how the institution will review records and exceptions.
- 03 / Validate
Test with your team.
Walk through representative applicant and staff tasks. Check the agreed handoffs, resolve outstanding questions and record what the institution accepts.
- 04 / Launch
Launch with a clear handoff.
Agree launch responsibilities, the work remaining with your team and where to turn for product help or additional implementation assistance.
Give the move a defined scope
Your admissions
migration checklist.
Historical migration and ongoing integration answer different questions. A migration plan should describe the information being transferred and the evidence your team will use to accept it.
Explore ongoing SIS handoffsAgree these items before the move.
- Inventory the records and source systems
List the people, applications and source identifiers you want to move. Separate current-cycle work from historical records and identify what will remain in the existing system.
- Define documents and history in scope
Identify the supporting documents, form configuration and history your team needs. Confirm what can transfer and how staff will access anything retained elsewhere.
- Agree mappings and data cleanup
Document how terms, programs, statuses and identifiers should map. Assign an owner for duplicates, missing values and other issues in the source data.
- Choose validation cases and acceptance criteria
Select representative applicant files and staff tasks. Agree how to compare results, record exceptions and decide whether the migrated information is ready to use.
- Plan cutover around the admissions calendar
Identify deadlines and active applications that affect timing. Record when updates stop or change systems, which system is authoritative and who approves live use.
- Prepare people and the support handoff
Name the staff who will maintain the application and handle applicant questions. Confirm training, unresolved work and the agreed route for help after launch.
Your agreed migration scope defines which records, documents and history transfer, how your team validates them and what remains in the source system.
The people who will run it
Choose the help
that fits your team.
Some institutions want Advant to lead the initial work. Others want guidance while their own team builds. The implementation conversation should make that division of work clear.
Guided
Your team leads configuration with guidance from Advant at agreed stages.
Work through the process with scheduled help.
Self-guided
Your team manages the move using implementation resources and a defined plan.
Institutional ownership, with a clear route to help.
Agree the deliverables, training, staff responsibilities and scheduled assistance for the approach your team chooses.
Prepare the next Form Owner, too.
Form work is often seasonal. Training should help a staff member understand the task months later, or help a colleague take it over.
Use real configuration work to practice the loop: make a draft change, review its impact, test the rule, preview the applicant experience and publish deliberately. Form-use signals then help the team decide what to revisit.
See application improvement in contextKeep support and project work clear.
Understanding a feature or reporting a product problem is different from asking Advant to design an institutional process or build a configuration.
The agreed service should explain the route for ordinary product help and defects, the help included with implementation and how additional work is scoped.
Review support hours, response expectations and escalation contacts as part of the service agreement.
Institutional participation
Bring the people
who know the work.
The same person may hold more than one responsibility. The useful question is who can make a decision, perform the work and accept the result.
- Admissions decision owner
- Sets the required process, resolves policy questions and approves institutional choices.
- Form Owner
- Understands application configuration, practices changes and keeps the ongoing process understandable.
- IT / SIS lead
- Coordinates access, data definitions and the institution's connected systems.
- Test participants
- Try the agreed applicant and staff scenarios and review the results before launch.
A reviewable proposal
Understand the scope
behind the cost.
A useful proposal accounts for the software, the work to launch it and the services your institution will use. Bring the application paths, campuses, systems and level of assistance you have in mind.
Discuss cost and scopeMake the assumptions visible.
- Software and ongoing support
State the charging basis, included product scope and agreed support terms.
- Implementation and migration
Identify one-time work, institutional inputs and the selected level of assistance.
- Integrations and connected services
Identify any separate setup, maintenance or provider charges that apply.
- Changes and additional campuses
Explain how a change in scope affects the work, price and planned schedule.
Review usage assumptions and renewal terms alongside the work and services included in your proposal.
For your institutional evaluation
Bring your security
and data questions.
Admissions, IT, accessibility and procurement may each need different evidence. Identify the questions your institution must resolve and the people reviewing them.
Access and permissions
Crossroads uses scoped staff permissions and keeps applicant access tied to the appropriate records. Review who needs access, what they can do and how responsibilities are assigned.
Data and operation
Work through hosting, data handling, retention, export, incident responsibilities and recovery requirements for the service your institution will use.
Product accessibility
Discuss the applicant and staff experiences your institution needs to assess, the evidence required and the people who will review it.
Your next admissions cycle
Let's talk through
the move together.
Bring your process, your calendar and the questions your team needs answered.