An ERP change often begins with a long feature list. A better first question is: which workflow should work from beginning to end? Ordering a configured product, purchasing missing materials, manufacturing the order and reviewing the invoice make a useful test of a new core.
Context is the test
Choose a representative order. Note where information is entered twice, who waits for clarification and which data is authoritative. Another interface will not automatically fix these handoffs. What matters is whether customer requirements, the bill of materials, stock and documents stay connected.
Clarify before migrating
Before migration, define responsibility. Which source owns the product? Which pricing rule applies? Who confirms a delivery date? Uncertain mappings belong in front of a human decision. An import alone does not establish a working business process.
Include an exception. What happens when material is missing or a customer change affects the bill of materials? This reveals whether the team has enough context to make its next decision.
What the October start means
HEINI ERP starts from October 2026 with an agreed scope for each implementation. Functions, migration, integrations and acceptance are defined in the individual proposal. The date does not promise complete coverage of every ERP project.
Existing ERP systems can remain authoritative. The existing Odoo connection remains an option too. The right choice depends on your business and the first measurable benefit.
A useful first meeting
Bring a typical workflow and the systems involved. Sensitive production data is not required. The aim is a clear first use case with responsible people, assessable results and agreed acceptance.