Implementation process
Five steps from discovery to go-live
Each step has a defined output. The line between standard, configured, custom and integrated work is drawn before anything is built.
- 01Business Discovery
- 02Process Mapping
- 03Configuration
- 04Data Migration & Training
- 05UAT & Go-Live
- 1
Business Discovery
3 outputsWe sit with the owner and department heads to understand how enquiries, projects, production, installation, billing and people actually flow today, and where control is lost.
- 2
Process Mapping
3 outputsEach workflow is written down as it will run in ClassicNext: who does what, at which step, with which document. This becomes the agreed scope.
- 3
Configuration
3 outputsCompany, users, roles, masters, print formats, workflows, notifications and dashboards are set up to the agreed maps.
- 4
Data Migration & Training
3 outputsOpening balances and master data are migrated from your current systems. Users are trained by role, on your own data, with their real documents.
- 5
UAT & Go-Live
3 outputsYour team runs real transactions end to end in a test environment, signs off, and we go live with hyper-care support in the first weeks.
Outputs at each step
- 1
- Current-process walkthrough
- Pain points by department
- Module shortlist and rough scope
- 2
- Process maps per department
- Document and approval flows
- Gap list: standard vs configured vs custom
- 3
- Masters and chart of accounts
- Roles and permissions
- Print formats and reports
- 4
- Master data and opening balances
- Role-based training sessions
- User guides for daily work
- 5
- Scripted user acceptance tests
- Go-live checklist and cut-over
- Post-go-live support window
- Steps
- 5
- Defined outputs
- 15
- Scope categories
- 6
- Team, start to support
- 1
Realistic boundaries
Included, and scoped separately
- Configuration of existing ERP capabilities to the agreed process maps
- Standard workflows for the modules in scope
- User roles and permissions
- Standard reports and dashboards
- Standard print formats with your letterhead
- Initial master data and opening balance migration from templates you fill
- Role-based training and UAT support
- Go-live support for the agreed hyper-care period
- Custom modules or documents that do not exist in the core ERP
- Custom workflows beyond the agreed scope
- Third-party integrations (WhatsApp API, biometric devices, e-way bill / GST portals, payment gateways)
- Mobile app development beyond the standard mobile-friendly interface
- Customer or vendor portals beyond standard functionality
- Advanced BI or data warehouse work
- Large or historical transaction-level data migration
- Custom hardware, on-site deployment and server setup
- Special compliance integrations
Scope categories
Every proposal is broken into six categories
- 01Standard
- 02Configuration + industry workflow
- 03Custom development
- 04Integration
- 05Data migration
- 06On-site services
- 01Configuration of existing ERP capabilities. Included in the package price.
- 02Your signage or project workflow set up around standard capabilities: naming, statuses, approvals, print formats, dashboards. Included as agreed in the process maps.
- 03New functionality or a materially different workflow that does not exist in the core ERP. Scoped and priced separately before work starts.
- 04External systems, APIs or hardware: WhatsApp API, biometric devices, GST or e-way bill portals, payment gateways. Priced per integration.
- 05Master data and opening balances are included. Historical or complex legacy transaction data is scoped separately.
- 06Travel and physical on-site implementation days beyond the remote plan are charged at actuals or a pre-agreed rate.
FAQ
Implementation: common questions
What do we need to prepare before discovery?
Nothing formal. Bring the people who run sales, projects, factory, installation and accounts, and the documents you use today: a quotation, a PO, a job sheet, an invoice. We work from real examples.
Can we go live module by module?
Yes. Many businesses go live with Finance, CRM and Sales first, then Manufacturing and Projects. The platform is the same, so nothing is re-entered.
What happens after go-live?
A hyper-care window with daily contact, then a support or AMC plan sized to your users and modules.
Who owns the data?
You do. Data can be exported from the system at any time in standard formats.
Start with a discovery call
Thirty minutes to understand your process and say honestly which modules, which package and which boundaries apply.
Prefer to start smaller? Get a process audit or request pricing.