Working session and plan
We map your processes, users and integrations and translate that into an implementation plan: milestones, who does what, and when you go live. You know where you stand before you start — cost included.
Implementation approach
ERP implementation without surprises: five fixed steps.
The biggest worry in an ERP switch is not the software but the transition. That is why every Valnovi implementation follows the same playbook: five fixed steps, one point of contact and a milestone plan you receive up front.
Configuration
We set up Valnovi for your processes: modules, rights, document templates in your corporate identity and the shop-floor screens. You review along the way, so there are no surprises at the end.
Data migration
Items, BOMs, contacts and open orders migrate following a fixed playbook. Every step is checked, so you start with data that is right.
Test run
You run a test period parallel to your current system, with real orders and real users. You only switch for good once the numbers match.
Go-live with support
The switch happens with support on the shop floor — not a remote helpdesk. After that, support takes over: people who help build the product themselves.
Implementation approach
What this means for you
One fixed point of contact
From the first working session until after go-live you talk to the same person — someone who knows the product itself.
A milestone plan up front
You receive the playbook and the milestones before you sign, not after.
A price without surprises
You know the cost, the timeline and who does what before you sign; extra work only happens after your approval.
Implementation approach
How long does it take?
The lead time depends on data migration and integrations. You receive a milestone plan up front; in the demo you hear a concrete lead time for your situation.
Implementation approach
FAQ
Can we keep working during the implementation?
Yes. You keep working in your current system until go-live; the test run happens in parallel. The switch is one agreed moment, not weeks of limbo.
How does the data migration work?
We migrate items, BOMs, contacts and open orders following a fixed playbook, and run a parallel test period. You only switch for good once the numbers match.
What does the implementation ask of our own team?
An internal point of contact, time to supply and check data, and users who join the test period. That is not a side issue: the implementations that succeed are the ones where the team is involved.
How long does an implementation take?
That depends on the amount of data and the integrations. In the demo you get a concrete lead time and a milestone plan for your situation.
Also read: the ERP selection roadmap with downloadable checklist →
Also read: what does an ERP system cost? →
Implementation approach
Book a demo
Want to see what this looks like for your company?
Book a demo or working session — we make the steps and the planning concrete for your situation.