Deutsch (Deutschland) 
Polski (PL) 
Marketplace · Data migration out of IFS · MIG-EXT-001
IFS Data Handover
Migration of your data out of IFS into a new ERP, with an extraction kit as the entry point: one script per data object, a field dictionary built from your own metadata, queries that flag duplicates and gaps, and a workbook that reconciles four figures after every cycle and checks that access filters did not silently cut the result. During the pilot I deliver the kit together with the service and run the extraction with your team. Data is only read from the source database; nothing is written to IFS.
- In the pilot, covers IFS Applications 7.5–10 and IFS Cloud, hosted by you or managed by IFS
- Data is only read from the source database; nothing is written to IFS
- In the pilot, selection criteria are parameters, so every run is repeatable
- Target ERP does not matter: the kit produces files, the target consultant maps them
1.Why does moving data out of IFS stall the new ERP project?
The consultant who loads your new ERP can only map what they understand, and an IFS database holds years of customers, suppliers and parts, with duplicates and with fields whose meaning exists only in your IFS configuration. When the extract arrives without that explanation, every trial import returns a list of questions and the cutover date moves. A second cause is silent: IFS views filter rows by company and site, so an extraction can return fewer rows than exist, without any error message.
2.What does the migration out of IFS service cover?
The migration out of IFS service starts with a scope and schedule workshop and then runs in cycles: extraction, consultations with your users and with the target-ERP consultant, support during cleansing, and export corrections after each trial import. The workshop is step 1 of the service and has no separate price. I quote the service after it, when the data objects, selection criteria and cycle schedule are known.
Mapping, transformation and import stay with the target-ERP consultant. IFS Data Handover follows the file contract of the service: exports repeat with the same result because the selection lives in script parameters and not in hand-edited files.
3.What is the kit, and why is it the entry point?
The IFS Data Handover kit is the extraction part of the service: scripts, a field dictionary and a reconciliation workbook that produce files in a fixed format, with every field described, for the migration consultant of your target ERP. It is the entry point because it is what you buy first, and everything after the extraction, from cleansing to trial imports, works on the files it produces. It fits a company that moves from IFS to SAP or another ERP and has a consultant on the target side who does the mapping and the import.
The kit is in pilot: I deliver it to the first clients together with the service, and I run the extraction with your team. You receive the scripts, the field dictionary, the reconciliation workbook and the output files. It is not a product you buy and run on your own yet.
4.Kit price and pilot terms
| Part | Price | How it is settled |
|---|---|---|
| Kit, the entry point | 2 500 EUR one-time per company | Regular price also for pilot clients, without a discount |
| Service, starting with the scope and schedule workshop | Quoted after the workshop | Workshop, cycles, consultations and support during cleansing |
Order of steps: step 1 is the workshop, which fixes the data objects, selection criteria and cycle schedule before the first script is written; step 2 is the extraction with the kit on that basis. The service is quoted after the workshop.
Delivery: during the pilot, together with the service; I run the extraction with your team.
Pilot condition: your consent to name your company as a reference after the target ERP goes live. Self-service purchase of the kit, without the service, opens after the pilot. There is no date for it.
5.Which IFS versions and hosting models does the kit cover?
In the pilot, the kit covers IFS Applications 7.5–10 and IFS Cloud, whether the database is hosted by your company or the system is managed by IFS. In every setup data is only read from the source database, and nothing is written to IFS.
| IFS setup | Hosting |
|---|---|
| IFS Applications 7.5–10 | Database hosted by your company |
| IFS Cloud | Database hosted by your company (Remote deployment) |
| IFS Cloud | Managed by IFS |
6.Key features
IFS Data Handover is delivered in the pilot together with the service, and it has these features.
- Schema comparison first - the first run compares your schema with the reference schema the scripts are built and tested against in the pilot, so a renamed or changed column shows up before the first export and not in the target ERP.
- One script per data object - customers, suppliers, parts, projects and open balances, with the selection criterion (for example customers with a purchase in the last 5 years) as a parameter.
- Field dictionary from your metadata - generated from the metadata of your IFS installation, so it follows your system and not a fixed list.
- Duplicate and gap flag queries - the matching rules (name, tax number, address) are configurable, and the flags travel with the export so your users meet them at the start of cleansing.
- Reconciliation workbook - the four figures after each cycle: records in IFS per criteria, duplicates merged, records excluded with a reason, records in the target ERP after import.
- Completeness check - compares the row count the extraction returns with a count from an IFS report.
- Access checklist - what to arrange, with whom and in what order, before the first run.
7.Why does the kit check completeness against access-filtered views?
IFS views filter rows by company and site, so an extraction can receive fewer rows than exist, with no error message. An export that is silently short makes the first reconciliation figure, records in IFS per criteria, wrong from the start. In the pilot, the completeness check compares the count returned by the extraction with a count from an IFS report. The figures match or the difference is explained; otherwise the cycle is not closed.
8.What is in the kit and what is not?
The table lists what IFS Data Handover contains when it is delivered in the pilot together with the service.
| Element | In the kit | Note |
|---|---|---|
| Schema comparison step | Yes | First step of every use of the kit on a new IFS system |
| Extraction scripts per data object | Yes | Customers, suppliers, parts, projects, open balances; selection criteria as parameters |
| Field dictionary | Yes | Generated from your metadata, custom fields included where the system exposes them |
| Duplicate and gap flag queries | Yes | Matching rules configurable |
| Reconciliation workbook | Yes | Four figures per cycle, plus the completeness check |
| Access checklist | Yes | Per IFS version and hosting model |
| Object register, decision log, contact list, cycle schedule | No | Process documents, see Implementation Documentation |
| Scope and schedule workshop, consultations, cleansing with your users, export corrections after trial imports | No | Part of the migration out of IFS service, quoted after the workshop |
| Mapping to the target ERP, transformation, import | No | Done by the target-ERP migration consultant |
9.What do you need for the extraction?
- Access to the data of the IFS system you migrate from, arranged as described in the access checklist.
- An IT contact who arranges the access and keeps the output files inside your company.
- A target-ERP migration consultant who maps the files.
- Business users from sales, finance and projects who cleanse and accept the data.
Data is only read from the source database. By design, business data lands only in the output files at your company, never in logs, so share those files only with the people who clean and map them.
10.Frequently asked questions
Can I buy and run IFS Data Handover on my own now?
No. IFS Data Handover is in pilot, and the kit is delivered to pilot clients together with the service while I run the extraction with the client's team. Self-service purchase of the kit opens after the pilot, and there is no date for it.
What does a pilot client pay and give in return?
A pilot client pays two things: the regular price of the IFS Data Handover kit, 2 500 EUR one-time per company, without a discount; and the service (scope and schedule workshop, cycles, consultations, support during cleansing), which is quoted after the workshop. In return the client consents to be named as a reference after the target ERP goes live.
Does IFS Data Handover work for IFS Cloud managed by IFS?
Yes, in the pilot. IFS Data Handover covers IFS Cloud managed by IFS. Data is only read from the source database; nothing is written to IFS.
Does IFS Data Handover install anything in IFS?
No. Data is only read from the source database; nothing is written to IFS and nothing is installed in it, so IFS Data Handover leaves no objects to review at the next IFS update.
Does the field dictionary include our custom fields?
Where the system exposes them, yes. In the pilot I generate the dictionary from the metadata of your IFS installation, so it includes custom fields where they exist: views ending in _CFV and columns starting with CF$_, which IFS Applications has from version 8 and IFS Cloud keeps. IFS Applications 7.5 has no custom fields.
Why not use the Data Migration Manager to export from IFS?
The IFS Data Migration Manager loads data into IFS, and its export function moves job definitions between environments, not business data. Leaving IFS therefore needs a separate extraction, which is what IFS Data Handover provides.
Who maps the exported files to the new ERP?
The migration consultant of the target ERP. IFS Data Handover delivers a fixed file format with a described field set, and mapping to the target ERP's templates, transformation and import are done on the target side. The IFS consultant stops at the described file.
Where does the business data from the extraction end up?
Only in the output files at your company. By design, IFS Data Handover keeps business data such as supplier names, prices and addresses out of its logs, and the logs are to hold only object keys, so they can be shared without exposing your data.
11.About the author
Dariusz Myśliwiec: independent IFS consultant, 18 years on IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, working remotely across Europe and globally. You talk to the consultant who writes the extraction scripts.
Selected IFS clients: 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. SAP is a registered trademark of SAP SE; this practice is not affiliated with SAP SE.
Check your IFS setup before the pilot
Tell me which IFS version you run and how it is hosted. On a 30-minute call I tell you what the extraction needs in that setup and whether you want to join the pilot. No pitch. Talk to the consultant who builds it. The scope and schedule workshop that follows is step 1 of the migration service, which is quoted after it.
