Who this suits
Businesses moving a defined operational process into ERPNext.
When a simpler option is a better fit
An ERP rollout is premature when transaction rules and ownership are unresolved; standardise the process before migrating.
Implementation approach
Select the first modules and document current records
Clean and trial-import masters and opening balances
Train operators and rehearse go-live with a rollback decision
Illustrative operating rules
Module selection, migration, training, and go-live readiness plan
Illustrative design example. Adapt these rules with the responsible team before implementation.
| Record or decision | Illustrative rule | Accountable owner |
|---|---|---|
| Module scope | Begin with agreed sales, purchasing or stock transactions | Business sponsor |
| Migration rehearsal | Reconcile counts, balances and representative records | Finance and data owners |
| Go-live gate | Approve permissions, training and recovery readiness | Project owner |
Dependencies and access
- Process definitions and module priorities
- Source exports and data-cleaning responsibility
- Hosting, administration and training owners
Limits and exceptions
Do not migrate every historical field by default. Keep a read-only archive where appropriate and verify opening balances with the responsible accountant. Availability and implementation scope require an enquiry.
Scope and cost drivers
Budget separately for modules, data cleanup, migration, configuration, hosting, training and support. Website package prices do not represent ERP project prices.
Acceptance and measurement
Go-live acceptance requires reconciled data, completed operator tasks, tested role access and a named support owner. No promised duration is implied.
Questions before starting
What must be ready before implementation?
Process definitions and module priorities; Source exports and data-cleaning responsibility; Hosting, administration and training owners.
Product documentation
Documentation checked 11 October 2026. Access and costs must be confirmed for your account and intended workflow.
Discuss the scope and availability
Tell CraftDuka about the task, your current systems and the people who will use it. Our team is based in Nairobi and serves Kenya and East Africa. We will assess the fit and availability before agreeing a project.