Vai al contenuto
[ SOLUTIONS ] / [ CUSTOM ERP REPLACEMENT ]

We replace your 2000s custom ERP without trauma.

For companies with a 2000s custom ERP that no longer scales, the original developer is gone, integration with e-commerce and modern systems has become impossible. We rebuild the ERP with a modern architecture, preserve data and workflows, release module by module.

[ THE PROBLEM ]

What happens today.

In the 2000s many Italian companies had custom ERPs built to measure: ERP, warehouse, accounting, CRM all sewn together ad hoc. It worked, but today the software is stuck: original developer gone, undocumented code, integration with modern systems nearly impossible, business evolution stalled.

The most common mistake is 'let's replace it with SAP'. A high-end commercial ERP requires 18-36 months of implementation, 6-figure costs, and the loss of the specific workflows that make you competitive. The pragmatic alternative is to rebuild the custom ERP with a modern architecture, preserving the particularities that work.

We do it module by module: accounting, warehouse, orders, invoicing are migrated separately, each with its own progressive go-live. Historical data is migrated with consistency checks. The old ERP stays operational until the new one is validated. No big-bang, no Hail-Mary weekends.

Replacing the ERP does not mean erasing the last 20 years. It means carrying them into an architecture that will hold the next 20.

[ HOW IT WORKS ]

The solution, broken into parts.

  • Discovery + functional audit: 4-8 weeks

    We map the current ERP: modules, workflows, data, integrations. We tell apart what is actually used from what exists but is dead. We identify the particularities that must be preserved vs the accidental complexities we can eliminate.

  • Modern modular architecture

    Modern stack (TypeScript, PostgreSQL, microservices when they make sense). Modular architecture enabling progressive release. Standard APIs, no vendor lock-in, no opaque proprietary databases.

  • Data migration with checks

    Migration of historical data from the old ERP to the new one, with automatic verification scripts (record count, accounting totals, referential integrity). Differential migration for data that changes continuously.

  • Module-by-module release + parallel run

    Each module goes into production in parallel with the old ERP, automatic reconciliation, cutover only after weeks of alert-free parallel run. Rollback criteria defined for every module.

[ WHO IT'S FOR ]

The typical profiles who benefit.

  • Manufacturing SMEs with 50-300 employees

    Companies with 2000s custom ERPs, original developer gone, evolution stalled for years. Typically looking for SAP/Oracle alternatives that do not destroy existing workflows.

  • Distribution and wholesale

    Wholesalers, distributors with custom ERPs integrated with warehouse, customer EDI, B2B e-commerce. The old ERP does not integrate with modern marketplaces and blocks the connection to digital channels.

  • B2B services with integrated CRM/ERP

    Service companies (ICT, facility, consulting) with custom CRM/ERP: project management, time tracking, consulting billing. The system holds up but evolution is stuck.

[ WHAT WE NEED ]

Transparency on what the client does.

Before we start we need a few accesses and decisions. All reasonable, no surprise asks.

  • Access to the current system

    • Read access to the old ERP database
    • Source code of the old ERP (even fragmentary)
    • Existing documentation, report queries, configurations
  • Internal knowledge

    • Power users of each module for discovery sessions
    • Point of contact for scope decisions
    • History of significant changes and customizations
  • Operational decisions

    • Module priority (what to modernize first)
    • Possible cutover windows (holidays, low seasons)
    • Compliance constraints (GDPR, e-invoicing, NIS2 if applicable)
[ TIME AND COST ]

Indicative numbers, not quotes.

TIME
Discovery 4-8 weeks. Full migration 9-18 months depending on complexity.
COST
Discovery €15,000-40,000. Full migration €100,000-400,000 for mid-sized companies. Range €200,000-700,000 for heavily customized ERPs with many integrations.
MODEL
Discovery on fixed milestone. Migration in modules with separate milestones, stop possible after every module without penalty.

Indicative numbers. For an accurate quote, let's talk.

[ FREQUENTLY ASKED ]

Answers to the most common questions.

Why not move to SAP or Oracle?

For Italian mid-sized companies, enterprise commercial ERPs (SAP, Oracle, Microsoft Dynamics 365) have total costs (license + implementation + customization) between €500k and €3M+, 18-36 months implementation, and typically force adapting business workflows to the software (not the other way around). Rebuilding custom costs 1/3 to 1/2 and preserves competitive specificities.

How soon do we see first results in production?

Typically 4-7 months for the first module in production (e.g. invoicing, orders). From there release is progressive: every 3-4 months a new module enters parallel run with the old one. Complete final go-live is typically 12-18 months from kickoff.

What happens if requirements change mid-migration?

We expect it. The modular architecture supports change requests without a total reset. Significant scope changes are evaluated at milestone boundaries, with an impact estimate on time and cost. The stop-after-each-module option means you can re-prioritize mid-flight.

Is historical data safe during migration?

Yes. Three layers of guarantee: (1) the old ERP stays operational in parallel for 6+ months post-cutover; (2) full pre-migration backups and incremental snapshots at every phase; (3) automatic data-consistency checks (record count, accounting totals, referential integrity) before considering a module migrated.