Demo

Implementation & go-live

A clear path from signed agreement to daily operations — who does what, how long it typically takes, and how we migrate you off legacy ERP.

Timelines depend on scope — but we design for phased go-live, not a big-bang wait. Most campuses are running payroll or fees within a few weeks of kick-off; broader suites follow in planned waves. Exact dates are fixed during discovery.

Delivery method

Five phases to production

Discovery

1–2 weeks

Map your campus, legacy systems, and success criteria before configuration begins.

Tuling team

  • Kick-off workshop with HR, finance, registrar, and IT stakeholders
  • Role matrix and entitlement mapping across products
  • Legacy ERP / spreadsheet inventory and data migration scope
  • Integration requirements — biometric, Tally, payment gateway, messaging

Your institution

  • Nominate a project sponsor and module owners per department
  • Share SOPs for leave, payroll, fees, admissions, and approvals
  • Provide sample exports from existing systems for migration analysis

Configuration

3–6 weeks

Translate your SOPs into workflows, entitlements, and integrations inside your tenant.

Tuling team

  • Tenant provisioning, subdomain, and branding setup
  • Workflow configuration — leave rules, approval chains, fee structures
  • Master data load — departments, designations, programs, fee heads
  • Integration setup and UAT environment access

Your institution

  • Validate configuration against campus policy in review sessions
  • Supply corrected master data and sign off workflow rules
  • Connect IT for device, gateway, and network allow-list coordination

Pilot

1–2 weeks

A controlled subset of users runs real workflows before institution-wide rollout.

Tuling team

  • Pilot user onboarding and desk-specific training sessions
  • Defect triage and configuration adjustments from pilot feedback
  • Parallel-run support where finance or HR needs overlap with legacy

Your institution

  • Select pilot departments (often HR + accounts + one academic desk)
  • Execute daily tasks in Tuling and log issues with module owners
  • Sign pilot exit criteria before go-live scheduling

Go-live

1 week

Cutover, institution-wide access, and training for remaining staff.

Tuling team

  • Production cutover plan and final data migration (if applicable)
  • Go-live war room support during critical cycles — payroll, exams, fees
  • Role-based training for remaining portals and self-service users

Your institution

  • Communicate go-live dates and support channels to all staff
  • Freeze legacy data entry on agreed cutover date
  • Escalate blockers through the nominated project sponsor

Hypercare

2–4 weeks

Elevated support after go-live while staff build muscle memory on the platform.

Tuling team

  • Priority ticket handling for post go-live issues
  • Configuration tuning from real-world usage patterns
  • Office hours for HR, finance, and registrar power users

Your institution

  • Collect feedback from departments and route through module owners
  • Track adoption metrics — logins, approvals completed, payroll signed off
  • Plan phase-two modules or campuses after stabilisation

Enablement

Role-based training

Training is desk-specific — not one generic slideshow for 200 staff who will never use the same screens.

Audience Coverage
HR & payroll Attendance, leave, compensation, payroll runs, statutory exports, employee self-service
Finance & accounts Fee collection, GL postings, Tally Connector, BI Connect refresh, counter desk
Registrar & academics Admissions, course registration, examinations, no-dues, student records
Management desks Approvals, HR AI Assistant, governance dashboards, audit review
IT Admin Tenants, entitlements, integrations, API keys, user provisioning

Recordings and quick-reference guides are provided for staff who join after go-live. Train-the-trainer sessions are available for larger campus groups.

Legacy ERP

Migration from existing systems

Most institutions are not starting from zero — they have Tally, an older campus ERP, spreadsheets, or a patchwork of tools. We scope migration during discovery and execute during configuration and go-live, with validation checkpoints before cutover.

  • Employee master, salary structures, and leave balances from legacy HRMS or spreadsheets
  • Student records and program structure where SIS is in scope
  • Fee heads, outstanding balances, and receipt history for finance cutover
  • Chart of accounts mapping for institutions moving from Tally-only or fragmented tools
  • Historical data depth is scoped per engagement — full history vs. opening balances only

Typical timelines to go-live

Hypercare support continues after go-live — these ranges are when staff start working in production, assuming timely data and sign-offs.

  • Focused start

    6–8 weeks

    HCM or Financials first — payroll, attendance, or fee counter live while the rest is phased.

  • Core suite

    8–12 weeks

    HCM + Financials + Tally / biometric / payment integrations at one campus.

  • Full platform

    12–16 weeks

    SIS, admissions, HCM, and finance together — still one campus, delivered in waves not a single freeze.

Multi-campus groups reuse configuration from campus one — additional sites often go live in 4–6 weeks each, in parallel where IT and data allow.

Discuss your timeline View engagement models