Switching & migration
Switch school software. Parents hear nothing routine until you go live.
A responsible migration needs two safeguards: review imported records before commit, and prevent routine messages from leaving while the school verifies its new workspace.Vidyapeeth360 provides a student CSV/XLSX mapping review plus quiet mode for non-essential outbound communication until the school explicitly goes live.
- Student CSV/XLSX mapping review
- Non-essential communication held in quiet mode
- 90-day full-term trial — no card
Five visible checkpoints from file to go-live.
Register your workspace
Pick your School Code, board and academic year. Self-serve, no card required.
Import with the Migration Copilot
Upload a student CSV or XLSX file. The mapping helper proposes columns and flags row-level validation issues for review.
Review before anything commits
You approve the mapping and preview the staged data. Only then does it commit — in one transaction, with a full audit trail.
Verify in quiet mode
New workspaces hold non-essential outbound communication while you explore, correct and train. Security OTPs and authorised staff invitations remain available.
Go live on your date
Flip go-live when you're ready. Configured reminders and parent communication can begin from that point; imported student records remain under onboarding safeguards.
Onboarding communication safeguard: quiet mode holds non-essential outbound communication while the school verifies its imported records. Security OTPs and authorised staff invitations remain operational exceptions; reminder and recovery eligibility should be confirmed in the migration walkthrough.
Compare migrations on evidence — what moves, what changes, and what your team must do.
Bring this checklist to every vendor conversation. It separates a promising feature name from the controls, boundaries and hand-offs that make it safe to operate.
| Decision area | What to verify | Vidyapeeth360 evidence |
|---|---|---|
| Student-record integrity | Ask how mappings, rejected rows, duplicate checks and rollback are handled before a bulk import commits. | CSV/XLSX mapping preview, row-level validation, review gate and one transactional commit. |
| Payment evidence | Trace how a provider event reaches an invoice, then how final bank credit and deductions are reconciled. | Provider callbacks update invoice evidence; final settlement remains a separate reconciliation step. |
| Onboarding communication | Identify which messages are held during migration and which operational exceptions remain available. | Quiet mode holds non-essential outbound communication; security OTPs and authorised staff invitations remain available. |
| Academic publishing | Verify grading configuration, mark limits, publish locks, report-card templates and correction handling. | Board-configured grading, server-side mark limits and locks after result publication; templates are reviewed during fit assessment. |
| Consent and retention | Review purpose, consent, retention, access, export and erasure workflows alongside the school's legal responsibilities. | Product controls support the school's DPDP programme; they are not legal certification or a compliance guarantee. |
| AI boundaries | Ask which sources, permissions, configured safeguards and human-confirmation gates apply to each AI surface. | Permission-scoped sources, configured identifier safeguards and confirmation gates for supported sensitive actions. |
Evidence describes the current product and its stated boundaries. Bring your source fields, providers, policies and required reports to a walkthrough for a fit review before rollout.
What stays true while you evaluate
Invoice-bound payment evidence
Fee collection runs through your school's connected gateway account; provider callbacks update the invoice, while your team reconciles final bank credit.
Data access and exit are documented
Each school's records are walled off by database-enforced isolation. Use supported exports while access is active, request erasure through the documented process — and the 90-day trial never becomes paid on its own.
Routine messages stay quiet until go-live
Quiet mode holds non-essential outbound communication. Security OTPs and authorised staff invitations remain operational exceptions.
The full security story — tenant isolation, AI privacy, consent and retention — is on the Security & Compliance page.
Bring a student CSV or XLSX. Review the move before commit.
Register free, preview the student import, and use the current 90-day trial to evaluate the workflows you need while non-essential communication remains in quiet mode.