Frequently asked questions

RATON is a business platform built by RATON SOFT. It combines ERP modules (sales, CRM, inventory, purchasing, finance, manufacturing, HR, reporting) with an integration layer, automation and an AI assistant. It is used as the operational core of a company, and as the target platform when moving off legacy business software.

Cloud deployment is supported as a deployment option. The concrete hosting model, region and responsibilities are agreed per project.

Local (on-premise) deployment is supported as an option for companies that require it. Infrastructure requirements are confirmed during the project.

Yes. Configuration covers most needs, and development is available where a business process genuinely requires it. We prefer configuration first, so that future updates stay straightforward.

Legacy software is a business system that still works but has become hard to change, integrate, support or staff. Typical signs are limited APIs, manual data exchange, a shrinking pool of specialists, and reporting that has moved into spreadsheets.

RATON is designed as a target platform for companies moving off 1C 7 or 1C 8. Whether it covers everything you use today depends on your configuration, customisations and country-specific requirements. That is exactly what the legacy analysis phase establishes, before any commitment.

Data migration from 1C 7 is a standard scenario in our methodology: master data, balances and an agreed depth of document history. The exact scope, effort and feasibility per entity are confirmed after analysing your specific database. We do not promise fully automatic migration.

Yes, 1C 8 is also a standard source in our migration methodology. Because 1C 8 installations are often heavily extended, the analysis phase focuses on which customisations are still used and how they map to RATON.

In eleven phases: discovery, legacy analysis, data mapping, process mapping, migration design, development, data migration, validation, user acceptance testing, go-live and support. Each phase produces something reviewable, and data is migrated into a test environment repeatedly before go-live.

Yes, and that is usually the goal for the processes that work. During process mapping we also identify flows that only exist because of legacy limitations — those are candidates for simplification rather than reproduction.

Yes. The AI assistant is part of the platform and works on your business data inside RATON. Which capabilities are active depends on your configuration and the modules you use.

Natural language business queries, search, report and document preparation, summaries, recommendations, anomaly hints, navigation, workflow assistance and data entry help. It prepares critical operations such as orders or postings but never executes them without explicit user confirmation.

RATON has an integration layer designed for accounting and fiscal exchanges, through API or structured files. Which systems are connected, and how, is confirmed per project — we do not list integrations as available before they are verified for your setup.

SAGA is part of the accounting integration scope we work with in Romania. The exact exchange format and scope are confirmed with RATON SOFT for your project before implementation.

e-Factura is part of the Romanian integration scope. Because the requirements change over time and depend on your document flows, the implementation scope is confirmed per project.

SAF-T reporting data is part of the fiscal integration scope. RATON structures operational data for it; the reporting responsibility and the exact scope are agreed with you and, where relevant, with your accounting provider.

There is no honest answer before the analysis. Duration depends on data volume and quality, the number of processes in scope, integrations and how much customisation the legacy system carries. We give a timeline in writing after the discovery and analysis phase.

We do not publish prices, because the cost is driven by your legacy system, data volume, number of users, processes in scope, integrations and customisation. After a short discovery call we can describe the scope and what drives the cost in your case.