Step 6 of 6 · Student intake and lifecycle

Student transfers

Move an active student between campuses, grades, or sections without losing the previous enrolment context.

Student transfers in LiveSchools365 Admissions

Student transfers is a Admissions workflow in the Student lifecycle area of LiveSchools365 school management software. Move an active student between campuses, grades, or sections without losing the previous enrolment context. Schools use it so A documented admission lifecycle with traceable decisions, complete student records, and controlled placement changes.

Move prospective learners from first inquiry through registration, record verification, promotion, and transfer. The people who typically work here are Admissions team, Administrator, Principal. The rest of the module stays one click away, so an inquiry, register, invoice, or stock movement does not have to be re-typed into another product.

What this workflow changes

Traceable campus movement This sits inside Admissions rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
Validated destination placement This sits inside Admissions rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
Reason and effective-date history This sits inside Admissions rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.

How it fits the rest of Admissions

Open these related Admissions guides when you want the step before or after Student transfers:

Admissions dashboard — Prioritize new inquiries, overdue follow-up, qualified applicants, and the next admission task.
Student inquiries — Capture family interest, desired placement, contact details, and follow-up status before creating a student record.
Student registration — Create the authoritative student, family, placement, health, and document record after an inquiry qualifies.
Student records — Find registered students, filter by placement, review details, edit records, and open the printable admission form.
Printed admission form — Produce the official admission form for review, signature, filing, or handover after registration details are verified.
Student promotions — Advance an enrolled student into the next academic year, campus, grade, and section while preserving placement history.

How schools evaluate this screen

During a demonstration or trial, Admissions team, Administrator, Principal should complete one realistic example: a new inquiry, a section register, a fee receipt, a notice, or a stock issue, depending on the module. Then confirm that the same record appears on the dashboard, the related report, and the next workflow. That is the test of a school ERP: one operational picture instead of parallel files.

Trend Developers can walk this exact screen against your admission, attendance, exam, or fee process. You can also start a 14-day trial and use the matching live form after sign-in.

All Admissions workflows · Start a trial · View pricing · Request a demonstration

Guide depth

Interface

Desktop interfaceComplete operational workspace with demonstration data

Traceable campus movement

Validated destination placement

Reason and effective-date history

Page anatomy

Fields, controls, and effects

Use this reference to understand what each area accepts and what it changes.

StudentSearch/select · Input

Purpose: Find the student by ID, code, name, or phone.
Rules: Choose the correct active learner.
Application effect: Loads the student to be transferred.

From campus / enrolmentSelect and optional number · Input

Purpose: Identify the placement being left.
Rules: Use the current campus and specify enrolment when history is ambiguous.
Application effect: Preserves the transfer origin.

To campus / grade / sectionCascading selects · Input

Purpose: Choose the authorized destination placement.
Rules: Select destination campus before grade and section.
Application effect: Creates the student's new placement.

Transfer date / reasonDate and text · Input

Purpose: Record when the move applies and why it was approved.
Rules: Use the effective date and a clear auditable reason.
Application effect: Explains the movement in student history.

Transfer registerSearchable table and row actions · Input and output

Purpose: Review source, destination, date, reason, and available corrections.
Rules: Verify both placements before editing or deleting.
Application effect: Provides a traceable transfer audit trail.