Moving from 1C to IFS Cloud
1C handles local accounting well, but a growing business runs into needs it was never built for: several legal entities, assets, projects, production. We move day-to-day operations to IFS Cloud, migrate master data and balances, and 1C can stay for statutory reporting if that suits you.
- Several 1C configurations are linked by data exchanges that keep breaking
- Every 1C update turns into its own project because of customisations
- Consolidation and management reporting are assembled by hand in Excel
- Maintenance, projects or production are tracked in separate spreadsheets
- Operations run in one system instead of a chain of data exchanges
- Platform updates no longer mean rewriting customisations
- Accounting keeps a familiar setup for statutory reporting
- Your team understands the new system and does not depend on the contractor
Four steps
Diagnose
Over 2–4 weeks we sort out which 1C processes and customisations the business really needs, and decide where statutory accounting will live.
Data clean-up
We assign an owner to each master-data set and clean up counterparties, items and fixed assets before migration, not after.
Build and trial runs
We configure IFS Cloud with a demo every two weeks and run several trial migrations, each ending with a balance reconciliation against 1C.
Go-live
We switch over at the start of a period and train users by role on your own data. After go-live we stay on to support the system.
Modules and platforms
Industries
Related insights
Moving from 1C to IFS Cloud: what to know upfront
Why companies outgrow 1C, which data to migrate, how to handle a parallel run, and how to keep local statutory reporting in view.
ERPOctober 27, 2026
4 min read
How an ERP implementation works: stages, roles and common mistakes
From diagnosis to post-go-live support: what happens at each stage, who owns what, and the mistakes that most often stall a project.
ERPSeptember 1, 2026
4 min read
Common questions
How long does an IFS Cloud rollout take?
The first phase usually takes 3 to 9 months, depending on the number of modules, sites and users and on how ready the data is. We give an exact plan after the diagnostic stage.
What does it cost?
The cost is the IFS Cloud subscription plus implementation work. The subscription depends on users and modules; the work depends on configuration, integrations and data migration. After the diagnostic stage we give an estimate and a five-year cost of ownership.
Can we keep 1C?
Yes. Often 1C stays for statutory accounting and tax reporting while IFS runs procurement, inventory, production, maintenance and management accounting. The two systems are integrated so nothing is entered twice.
Cloud or our own servers?
IFS Cloud can run in the cloud or on the company’s own servers. The choice depends on data-residency requirements, IT policy and budget. We compare the options at the design stage.
Do we have to roll out every module at once?
No. Most companies start with finance, procurement and inventory, or with asset management, and add other modules in later phases. It is one platform, so new modules work with the data already in it.
What happens after go-live?
In the first weeks after go-live we stay close to users and fix whatever gets in their way. After that comes support under a contract with clear response times, IFS updates and changes for new needs.