IFS Cloud data migration · Independent IFS Cloud practice
Five data migration risks that move an IFS Cloud go-live, and how to catch each one in time
An IFS Cloud data migration carries five risks: data quality, load order, the cutover window, personal data and history scope. Data quality, load order and the cutover window show up in trial loads before go-live, if the project is set up to look for them; personal data and history scope are decisions taken in the migration strategy.
Key takeaways
- Duplicates, obsolete parts and incomplete customer records are a data quality problem, and they are fixed in the source or in the cleansing rules before the load, not in IFS Cloud after go-live.
- Data moves in three layers: master data first, then open balances, then history only if the data migration plan lists it. Open balances are the time-critical layer in the cutover.
- The cutover window is a fixed number of hours. Trial loads are timed so the project knows before cutover whether the open-balance load fits in it.
- Personal data is a GDPR question at migration time: what is not needed in IFS Cloud is not migrated, and the staging area is secured like production.
- Closed transaction history stays out of the live IFS Cloud environment unless the data migration plan lists it, and goes to a read-only archive with a retention decision.
Data migration into IFS Cloud can move a go-live date late in the project, because its problems stay invisible until data is loaded and reconciled. A buyer opens a purchase order for a supplier that was merged in the source, or a trial balance does not match by the value of open invoices that were never loaded. This article lists the five risks I check for first and the evidence that shows each one early. For the tooling side, FndMig and the Data Migration Manager compared object by object, read the IFS Cloud Data Migration: FndMig & DMM Field Guide.
1.Why does data quality decide the migration?
Data quality decides the migration because IFS Cloud accepts a record that is technically valid even when it is a duplicate or obsolete, and from then on every purchase order, stock count and invoice uses it. A legacy system that has run for years holds duplicate suppliers, parts nobody has bought since a product line was dropped, and customer records without the fields the new process needs.
What cleansing looks like in practice
Cleansing is a set of written rules with an owner per business area, signed before the first trial load. A rule says what happens to a record: it is migrated as is, corrected, merged with its duplicate or left behind. The business owner of the data, the buyer for suppliers or the planner for parts, signs the rule, because only they can say which of two supplier records is the real one.
The migration is also the cheapest moment to standardise what the legacy system got wrong: units of measure, the chart of accounts and the supplier master. Carrying an inconsistent unit of measure into IFS Cloud means converting it in every interface and report afterwards.
Where IFS Cloud helps and where it does not
IFS Cloud migration jobs can use a conversion list to convert data before migrating, and the Data Migration Manager documentation on docs.ifs.com lists inbuilt data cleansing and validation among the benefits of that tool. The tool checks the rules it is given. Deciding which of two suppliers survives is still a business decision, and no load tool makes it for you. The ownership model behind those decisions is in The Data Migration Governance Checklist.
2.In what order should data move into IFS Cloud?
Data moves into IFS Cloud in three layers, because each layer depends on the one before it and each has a different validation requirement and a different deadline. Loading everything at once makes a failed load impossible to trace back to its cause.
| Layer | What it contains | What decides success | When it is loaded |
|---|---|---|---|
| Layer 1: master data | Customers, suppliers, parts, accounts | High validation requirement: duplicates removed, mandatory fields filled, owners signed off | Before cutover, with changes frozen or tracked from the load date |
| Layer 2: open balances | Inventory on hand, open payables and receivables, open orders | Reconciliation of quantities and values against the source at the cutover date | In the cutover window; this is the time-critical layer |
| Layer 3: history (optional) | Closed transactions kept for reporting | A retention decision and a way to retrieve documents, not a load into the live system | Only if the data migration plan lists it; otherwise archived outside IFS Cloud |
The load order inside each layer follows references: a part supplier record cannot load before both the part and the supplier exist, and an open purchase order cannot load before its supplier and parts. The detailed sequence for supply chain objects is in the FndMig and DMM field guide linked above.
3.Will the open-balance load fit in the cutover window?
The cutover window is the fixed time between stopping work in the legacy system and starting work in IFS Cloud, and the Layer 2 load has to fit inside it with time left for reconciliation. If the dynamic data load takes 48 hours but the business only has a 24-hour weekend window, the go-live does not happen that weekend.
The only way to know the load time is to measure it in full trial migrations, also called mock migrations, on production-sized data. IFS Cloud lets you view the history of executed migration jobs and, depending on the kind of error, restart a job for the error rows, as described in the IFS Cloud data migration documentation. The project records the duration of each object in every trial in its own run log, so the slow objects are found and tuned before the cutover weekend.
- Run a full trial load on a copy of production-sized data, layer by layer, in the order planned for cutover.
- Record the time per object in the run log, and the error rows to correct and restart.
- Reconcile counts and values against the source and write down every difference with its cause.
- Compare the total of load plus reconciliation with the agreed cutover window, and fix or re-plan the objects that do not fit.
- Repeat until a trial runs inside the window with a reconciliation the business owners sign.
The cutover plan itself, with its checklist and contingency steps, is part of go-live readiness, and the reasons to rehearse it are in Go-Live Is a Load Test.
4.How does GDPR change an IFS Cloud migration?
For an organisation in the EEA, a data migration copies personal data into new systems and staging areas, so the GDPR applies to the migration itself and not only to the finished IFS Cloud environment. Contact persons on customer and supplier records, employee data and delivery addresses are all personally identifiable information (PII).
Two principles in Article 5 of the GDPR (Regulation (EU) 2016/679), data minimisation and storage limitation, translate into migration rules. Personal data that IFS Cloud does not need is not migrated, and obsolete personal data is purged in the source, not carried across. The staging area where data is extracted and transformed is secured like production, access is limited to the people who work on the load, and personal data in test environments is anonymised or masked until the final production load. Where the staging area is located matters for data residency, so it is decided with the same care as the hosting of IFS Cloud. Your data protection officer confirms the rules for your company; this article is not legal advice.
5.Should closed history go into IFS Cloud?
Closed transaction history stays out of the live IFS Cloud environment unless the data migration plan lists it, because migrating it multiplies the volume to load and reconcile in every trial while new transactions in IFS Cloud do not reference closed ones. Loading closed history also forces old records through current validation rules, and each record that fails has to be analysed or overridden.
The alternative is a read-only archive outside IFS Cloud, sized by the retention periods of each legal entity and reachable through reporting tools for the people who need it. That decision, the archive routes and the switch-off date of the old ERP are set out in Legacy ERP After IFS Cloud Go-Live: Archive and Switch-Off.
6.Migration readiness checklist
A data migration is ready to start trial loads when four items are in place, and each one is a document or a decision you can check:
- Data owners assigned per business area, by name.
- Cleansing rules defined and signed off by those owners.
- Legacy system freeze date established and agreed with the business.
- Staging environment secured and compliant with the GDPR rules in section 4.
These four items go into the migration strategy, which also fixes the layers, the scope of history and the tooling. The Data Migration Strategy template (IDK-14) gives that document a structure to fill in for your project, and the Data Migration Plan and Readiness Checklist (IDK-15) carries the checklist per data object. For the step-by-step technical checks per phase, see the IFS Cloud Data Migration Checklist (2026 Edition).
7.Frequently asked questions
Should we migrate all 10+ years of historical transactional data into IFS Cloud?
An IFS Cloud data migration loads master data and open balances; closed transaction history is outside that scope unless the data migration plan lists it, and it is kept in a read-only archive outside the live environment. Loading deep history adds volume to every trial load and reconciliation, and old records have to pass current validation rules.
Which tools are used to migrate data into IFS Cloud?
IFS Cloud has two migration mechanisms documented on docs.ifs.com: migration jobs, which load data from a text file or an Oracle source such as a table, view or database link and keep a history of executed jobs, and the Data Migration Manager, which moves legacy data through containers with inbuilt cleansing and validation. When the source is not IFS or the data needs transformation before loading, it is extracted and transformed in a staging database first and then loaded into IFS Cloud with migration jobs.
How do you know the IFS Cloud data load will fit in the cutover weekend?
The load time for an IFS Cloud cutover is measured in full trial migrations on production-sized data, which are timed object by object in the project run log, and the total of open-balance load plus reconciliation is compared with the agreed cutover window. Objects that do not fit are tuned or re-planned before the real cutover.
How is personal data protected during an IFS Cloud migration?
Personal data in an IFS Cloud migration is protected by migrating only what IFS Cloud needs, securing the staging area like production, limiting access to the people working on the load, and anonymising or masking personal data in test environments until the final production load. For organisations in the EEA these rules follow the GDPR principles of data minimisation and storage limitation.
Who should own data cleansing in an IFS Cloud project?
Data cleansing in an IFS Cloud project is owned by the business, one named owner per area such as suppliers, parts or customers. The migration team builds and runs the rules, but only the business owner can decide which duplicate record survives and sign the reconciliation after each trial load.
8.About the author
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally. You talk to the consultant who does the work, not a sales layer.
Selected clients from my IFS work: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Writing the migration strategy for your IFS Cloud project?
The Data Migration Strategy template (IDK-14) turns the decisions in this article into one document for the steering group to sign: scope by data object, history depth, ownership, cleansing approach, load cycles and reconciliation, security of extracts and cutover implications.
See the Data Migration Strategy template (IDK-14) Read: FndMig & DMM Field Guide

Deutsch (Deutschland)
Polski (PL)