A standard SAP Business One implementation runs six weeks, in seven steps, for a fixed scope of ₹9,50,000 on standard modules and one legal entity. What moves that number is entities, customisation and data — not the software.
Seven steps. The order matters more than the labels: every one of them is cheap to get right early and expensive to fix later.
Weeks 1–2 discovery and scoping · weeks 2–4 configuration and data migration · weeks 4–5 training, UAT and parallel run · week 6 go-live with hypercare.
"Standard scope" is a real definition, not a hedge. It means the modules most businesses run — finance, sales, purchasing, inventory — on one legal entity, with GST returns, e-invoicing, digital signatures and one bank integration, migrating master data and opening balances, with role-based training for your team.
What takes it past six weeks is specific and knowable at blueprint: additional legal entities, non-standard modules, custom development, integrations beyond the standard bank and GST rails, and multi-year historical data migration. A partner who cannot tell you which of those applies to you before quoting has not done discovery properly.
The six weeks are ours; the elapsed time is shared. The schedule assumes your team is available for discovery workshops, that somebody owns master-data cleanup on your side, and that UAT sign-off does not wait three weeks for a decision. Projects that overrun rarely do so because configuration took longer — they overrun because a decision sat unmade. Naming a single decision-maker before kick-off is worth more to the timeline than any amount of extra consultant time.
₹9,50,000 for a fixed six-week scope on standard modules and one legal entity — quoted before the project starts, not discovered during it.
That figure includes digital signature, email and WhatsApp integration, GST and E-Invoice, a reconciliation tool, one bank integration, and QC. Additional legal entities, non-standard modules and custom development are quoted separately. If a competing quotation is lower, the first thing to check is which of those six lines it excludes.
On the cloud subscription plans, implementation is not a separate invoice at all — it sits inside the monthly figure. The full breakdown of licences, database, AMC, AMS and hosting is on the SAP Business One price in India page.
Three things move implementation cost more than anything else, and all three are decisions rather than facts about your business. Customisation is the largest: every deviation from standard is development now plus regression testing on every future upgrade, which makes a month-two decision into a year-three budget line. Entities come next — a second company code is consolidation logic and inter-company rules, not a copy of the first. And historical data is the quiet one: masters and opening balances are routine, but multi-year ledgers with batch and serial history are where migration effort concentrates.
The useful discipline is to ask, for each of those, what breaks if you do not do it. Plenty of customisation requests survive that question. A surprising number do not.
One team, one fixed scope, and an estimate given at blueprint rather than adjusted mid-project.
The people who scope the project are the people who deliver it. That sounds like a small thing and is not: the most common failure in mid-market ERP is a proposal written by one team and executed by another who were not in the room when the promises were made.
The experience behind it: 350+ implementations since 2006, across 32 industries and 30 countries, with a team of 60+ specialists and 20+ years of SAP work. Industry depth matters more than headcount here — a partner who has run your industry knows which questions to ask in discovery, which is where projects are won or lost.
Fixed scope is the other half of it, and it cuts both ways deliberately. You get a number that does not move; we carry the risk of having estimated it wrong. That only works if discovery is honest, which is why scope is fixed after the blueprint rather than in the proposal. A quotation issued before anyone has seen your processes is a guess wearing a number.
Every rollout ships India-ready as standard: GST returns, e-invoicing, TDS and TCS handling, digital signatures and bank integration. These are not add-ons quoted later — a system that cannot file is not live, whatever the go-live certificate says.
Moving an existing SAP Business One from SQL Server to SAP HANA is a migration project, not a reimplementation — your configuration and history come with you.
It runs in four stages: assessment of the current system and what HANA changes for it; data migration; testing against your own reports and processes; then go-live. The application is the same on either database, so users do not relearn the system.
Testing is the stage worth protecting. Custom reports, queries and any add-ons written against SQL Server are where a migration actually bites — the standard application moves cleanly, bespoke work does not always follow. An honest assessment lists that inventory before the project starts rather than finding it during cutover.
Whether it is worth doing is a separate question from whether it is possible. HANA is licensed by database memory size rather than user count and needs higher-specification hardware, so the case for it tracks data volume and analytics load rather than headcount. For a first ERP at 10 to 20 users, SQL Server is usually the right commercial choice.
The software is the same from every partner. The implementation is not, and that is what you are actually buying.
Four questions separate partners quickly. Have they implemented your industry, and can they name the customers? Who staffs your project — the people in the pitch, or a different team? Is scope fixed before you commit, or does it emerge as the project runs? And what does support look like in year two, when the implementation team has moved on?
Ask for references you did not choose from a list, in your own industry, and ask them one question: what went wrong, and what happened next. Every implementation has something go wrong. What separates partners is whether it was surfaced early or discovered by the customer, and a reference who cannot recall a single problem is either lucky or rehearsed.
Be equally careful with the lowest quotation. In this market a cheap implementation number usually means a narrow scope, and the difference reappears as change requests once you are committed and switching is expensive. Compare what is included line by line — GST and e-invoicing, digital signature, bank integration, data migration, training — before comparing totals.
The seven criteria worth checking, and the questions to ask on any partner's demo call, are set out in the guide to how to choose an SAP Business One partner.
350+ implementations is a number. These are three you can read in full, with the customer named.
The full set is on the case studies index, and the national picture on the SAP Business One partner in India page.
In seven steps: discovery, fit and blueprint, configuration, data migration, training, UAT and parallel run, then go-live with hypercare. Standard scope runs six weeks. The blueprint stage is where scope is fixed, so it is the stage worth spending time on rather than rushing.
SAP’s own methodology names five: project preparation, business blueprint, realisation, final preparation, and go-live and support. TEKROI runs the same shape as seven more granular steps, splitting realisation into configuration and data migration, and naming training separately because it decides adoption.
Implementation is quoted as a fixed scope: ₹9,50,000 for a six-week standard scope on standard modules and one legal entity. Additional legal entities, non-standard modules and custom development are quoted separately. On the cloud subscription plans, implementation is inside the monthly figure instead.
Six weeks for a standard scope: discovery in weeks 1–2, configuration and data migration in weeks 2–4, training, UAT and parallel run in weeks 4–5, go-live with hypercare in week 6. Multi-entity structures and heavy customisation take longer, and are estimated at blueprint rather than promised up front.
For day-to-day roles, yes — most users work in a handful of screens and are productive within a training cycle. Finance and system administration take longer because the depth is real. Role-based training on your own configured data, rather than a demo database, is what shortens the curve.
No honest answer names one firm for every business. Judge on industry evidence, who actually staffs your project, whether scope is fixed before you commit, and what support looks like after go-live — the full criteria are in our guide to choosing an SAP Business One partner. TEKROI has 350+ implementations across 32 industries since 2006, with named customers published as case studies.
Bring your entity structure, user count and the integrations you need. Scope is fixed at blueprint, before you commit.