Skip to main content
Schylva

School ERP implementation and onboarding

A clear school ERP implementation path—from first conversation to first school day.

Schylva turns your school's priorities into a written rollout plan covering initial migration, configuration, role-based validation, staff training, go-live and ongoing support.

No student records or confidential school data are required. We respond to demo and quote enquiries within two working days, excluding weekends and public holidays.

One connected rollout

Move from school context to validated live use through clear checkpoints.

See what your school prepares, what Schylva handles and what must be agreed before the next rollout milestone begins.

1 of 6: Understand

Understand the starting point

Understand the school before configuring the platform.

Review the academic year, board context, school structure, priority workflows and the people responsible for decisions.
Review the connected platform
School prepares
Confirm the academic year, board context, classes, sections, priorities and decision owners.
Schylva handles
Turn the school’s starting point into the questions that define a useful rollout scope.
Checkpoint before moving forwardSchool context and decision ownership are understood.

Included services and written plan

Know what is included—and what your school approves before activation.

Standard onboarding, initial school configuration, initial migration, staff training and ongoing product support are included. Migration details, validation checks, training arrangements, timing and go-live decisions are confirmed for the individual school in writing.

Included

Standard launch services

  • Standard onboarding
  • Initial school configuration
  • Initial data migration
  • Staff training
  • Ongoing product support

Confirmed in writing for the school

School-specific implementation detail

  • Agreed launch scope and owners
  • Source records and migration details
  • Configuration priorities
  • Validation and acceptance checks
  • Training arrangement
  • School-specific timing and go-live plan
  • Dedicated enrolled-school support route
Payment processing

Payment-gateway transaction charges remain separately payable under the selected provider’s applicable terms.

School communication

School updates use app notifications. Login verification SMS delivery is not currently available, and WhatsApp or non-login SMS are not supported product channels.

Shared ownership

Make ownership clear before configuration begins.

The school owns decisions and source information. Schylva configures and guides. Both sides review the result before live use.

School decides and provides

Keep school decisions and source information owned by the school.

  • Nominate a decision-maker and operational contacts
  • Confirm academic structure, roles and priorities
  • Provide agreed source information through the approved route
  • Make relevant staff available
  • Approve readiness for live use

Schylva configures and guides

Translate the agreed school context into the supported platform.

  • Translate the agreed structure into supported configuration
  • Prepare the account and role foundation
  • Complete the included initial migration within the agreed scope
  • Guide representative workflow validation
  • Provide included staff training and the enrolled-school support route

Both validate and approve

Use shared checkpoints before the school moves into live use.

  • Agree the implementation scope and owners
  • Review representative records
  • Test selected role workflows
  • Record exceptions, dependencies and actions
  • Confirm go-live readiness

Data and configuration readiness

Prepare the school context that must be reviewed before go-live.

Prepare the school structure and identify the people who can verify it. Initial records are provided only through the implementation route agreed with the school.

School context to review

  • Academic year, board context, classes and sections
  • People and guardian relationships
  • Roles and account foundation
  • Relevant fee, timetable, academic and reporting configuration
  • Priority launch workflows
  • A named school decision-maker, source-information owner and operational contacts
  • The approved route through which implementation information will be provided
Initial migration is included

The operational detail belongs in the written plan.

Initial migration is included. The records in scope, formats, method, rounds, validation steps and timing are confirmed in the school’s written implementation scope.

See what the school-specific plan confirms

Real product validation points

Review representative school and account context before go-live.

These Schylva screens use sample school data to show the records and account context a school can review during validation. Migration details remain in the school-specific written plan.

Actual product screen · sample school data
Administrator reviews fictional student, teacher, class and guardian records in SchylvaInspect school foundation

School foundation

Review representative people and school relationships.

The administrator overview makes the supported student, teacher, guardian and class context visible for school validation.Review student information

Rollout readiness

Bring a clearer starting point into the implementation discussion.

Use this private checklist to identify the school context worth bringing to the first rollout discussion. Final timing is confirmed only in the written plan.

Review what your school can bring to the rollout discussion.

0 of 7 reviewed
School rollout preparation items

Bring these items to the implementation discussion7 items still to review. You can discuss them with Schylva rather than deciding them alone.

See the 7 remaining items
  • A school implementation owner is identified
  • The approximate student count is known
  • Priority workflows are selected
  • The academic structure can be reviewed
  • A source-information owner is identified
  • Relevant school roles can join validation and training
  • A preferred launch window can be discussed

Selections are not saved or submitted.

Go-live readiness gates

The school begins live use after the agreed checks are visible.

  1. School structure reviewed
  2. Representative migrated records validated
  3. Relevant administrator and teacher workflows tested
  4. Parent and student access checked where part of the launch scope
  5. Relevant staff training completed as agreed
  6. Open actions and dependencies recorded
  7. School confirms readiness for live use

Training and launch access

Prepare the people who will validate each priority workflow.

Staff training is included. Administrators, teachers and relevant accounts or academic leads join the checks connected to their work. Parent and student access is validated when it is part of the agreed launch scope.

Coming at launch

Complete role experiences across web, iOS and Android.

Complete administrator, teacher, parent and student experiences across web, iOS and Android are coming at launch with the complete approved launch feature set. Mobile access follows the same school, account and role foundation validated during implementation.

Review the mobile-app launch plan
  • Available at launchWebConnected role experience
  • Available at launchiOSComplete mobile feature set
  • Available at launchAndroidComplete mobile feature set

Representative role checks

Validate the work teachers and families will actually see.

After go-live

Ongoing product support is included.

After go-live, enrolled schools receive ongoing product support. The 24–48-working-hour resolution target is separate from the two-working-day response for demo and quote enquiries.

IncludedOngoing product support

Ongoing product support is included after go-live.

Support hoursMonday–Friday · 10:00 AM–6:00 PM IST

Support excludes public holidays.

Resolution target24–48 working hours

Schylva targets resolving product issues within 24–48 working hours; this is not an unconditional guarantee.

When more time may be required

Dependencies remain visible

Additional time may be required when resolution depends on a third-party service, required school information or action, or circumstances outside Schylva’s reasonable control.

Enrolled-school route

Provided during onboarding

Enrolled schools receive their dedicated email or support route during onboarding.

Sales enquiries

Response within two working days

Demo and custom-quote enquiries receive a response within two working days, excluding weekends and public holidays. This is separate from the support-resolution target.

Sales enquiries: nikhil@remonthub.com. Enrolled schools receive their dedicated product-support route during onboarding.

Review security and access boundaries

Implementation questions schools ask

Practical answers before agreeing the school-specific plan.

What is included in Schylva implementation?

Standard onboarding, initial school configuration, initial data migration, staff training and ongoing product support are included. The school-specific written implementation scope confirms the launch scope, owners, migration details, validation checks, training arrangement, timing and enrolled-school support route.

How long does school ERP implementation take?

There is no universal implementation duration. Timing depends on the school’s size, preparation and source-information readiness, configuration breadth, agreed rollout scope, dependency turnaround and school decisions. The school-specific written implementation scope confirms the timing and go-live plan.

Do all Schylva modules need to go live at the same time?

No. Schylva’s complete approved launch feature set is available at product launch, while each school can prioritise the modules and role workflows in its written implementation plan. The sequence and readiness checks are agreed with the school before live use.

Will Schylva migrate our existing school data?

Yes. Initial data migration is included. The records in scope, formats, method, rounds, validation steps and timing are confirmed in the school’s written implementation plan. Representative migrated records are reviewed with the school before live use.

What should our school prepare before implementation?

Prepare the academic year, board context, classes and sections, people and guardian relationships, roles and accounts, relevant configuration and priority launch workflows. Identify a school decision-maker, source-information owner and operational contacts. Provide records only through the implementation route agreed with Schylva; demo and quote forms are not intended for student records or confidential school data.

Who should own the rollout inside the school?

The school should nominate a decision-maker, a source-information owner and the operational contacts needed for the agreed workflows. Schylva configures and guides the rollout, while the school reviews its structure, provides required decisions and confirms readiness for live use.

Is staff training included?

Yes. Staff training is included. Session count, duration, participants and delivery method are confirmed in the school’s written implementation scope.

Can board-specific report cards and grading rules be configured?

Yes. Schylva supports board-specific report-card formats and configurable grading scales for CBSE, ICSE and State Board school requirements. The school’s exact academic structure and reporting rules are reviewed during implementation.

How do the iOS and Android apps fit into rollout?

Complete administrator, teacher, parent and student experiences across web, iOS and Android are coming at launch with the complete approved launch feature set. The relevant role and access paths are reviewed as part of the school-specific rollout scope.

What support is available after go-live?

Ongoing product support is included. Support operates Monday–Friday, 10:00 AM–6:00 PM IST, excluding public holidays, with a target of resolving product issues within 24–48 working hours. Additional time may be required when resolution depends on a third-party service, information or action from the school, or circumstances outside Schylva’s reasonable control. Enrolled schools receive their dedicated support route during onboarding.

Does starting implementation secure the introductory offer?

No. Completing a demo, requesting a quote or starting an implementation discussion does not qualify a school. Qualification requires completed school-account activation by 31 March 2027 at 11:59 PM IST.

Plan around the school

Plan the rollout around your school’s real starting point.

Tell us your approximate student count, priority workflows and preferred launch window. No student records or confidential school data are required. Schylva responds within two working days, excluding weekends and public holidays, to confirm the right next conversation.

nikhil@remonthub.com