- Industry
- Manufacturing
- Legacy system
- 1C Enterprise 7 with in-house extensions
Demo case study. Illustrative scenario, not a real customer reference. Real references are provided on request once available.
Business problem
Production planning happened in spreadsheets because the legacy system could not link customer orders, bills of materials and material availability. Stock figures were corrected manually every week.
Migration
- Legacy analysis of the 1C 7 database and the spreadsheet layer around it
- Mapping of products, BOMs, warehouses and opening balances
- Three migration runs into a test environment before sign-off
- Parallel operation for one month on production orders
RATON solution
- Manufacturing, Inventory/WMS and Purchasing on one data model
- Production orders generated from sales demand
- Material shortages visible before the order is released
- AI assistant used for daily shortage and status questions
Result
Planning moved out of spreadsheets and into the platform, and stock corrections became an exception rather than a weekly routine. Figures are illustrative.
Lessons learned
- Migrate the spreadsheet layer too — it holds the real process
- Agree history depth early; it drives most of the effort
- Parallel operation is worth it for production
Case studies
How a migration looks in practice.
DEMO CASE STUDY
A distributor untangling years of customisation
- Industry:
- Wholesale
- Legacy system:
- 1C Enterprise 8, heavily customised
Ten years of extensions made upgrades impossible and every new sales channel required a custom export. Nobody could say with certainty which customisations were still in use.
Learn moreDEMO CASE STUDY
A retail chain leaving a single-developer application
- Industry:
- Retail
- Legacy system:
- Custom desktop application
The application had been maintained by one developer for years. Stock per store was unreliable, and any change request waited for a single person.
Learn moreReady to see what modernization looks like for your business?
Request a demo and we will prepare it around your current system, your processes and the questions your team actually has.
Prefer to talk first? Contact our team.