Interface IFS via Excel.
No development. No Data Migration Tool.
Export your IFS data into a structured Excel file, prepare your changes in the tool everyone knows, and reimport with confidence — every row validated before reaching IFS.
required
before import
Data Migration Tool
zero training
Importing data into IFS shouldn't cost €40,000 in consulting fees
Native IFS import is designed for technical profiles. It requires a deep understanding of internal structures, validation scripts, and accepted formats. For every import need, you call in a consultant — or worse, you give up.
The result: your business teams depend on IT for every reference data update. A simple need — updating 200 purchase items — triggers a ticket, an estimate, a quote. ERP Control makes your teams self-sufficient.
From export to import — a complete cycle, no development required
Every step of the Export → Edit → Import cycle is guided, validated, and tracked.
Structured multi-table export
Export any IFS table — or a set of related tables — into a structured, edit-ready Excel file. Export runs as a background task: the interface never freezes.
Excel column ↔ IFS field mapping
The interface guides your teams in matching each Excel column to the correct IFS field, with built-in format checks. No more guessing the structure — the system walks you through it step by step.
Line-by-line preview before import
Before anything is sent to IFS, each row is displayed with its status: valid, error, or warning. Fix or skip row by row — no more unusable global rejections.
Automatic dependency management
The module detects critical relationships between entities (e.g., an item linked to a category or currency). If a parent entity is missing in IFS, a precise alert is raised before the import — never after.
Automatic POST / PATCH / DELETE orchestration
ERP Control automatically determines whether each row should be created, updated, or deleted in IFS based on its actual state. No manual operation configuration — it's fully automatic.
Full history and 1-click relaunch
Every import is logged with status, errors, and validation messages. Relaunch a previous import, duplicate it, or review its details for an audit — without redoing the mapping from scratch.
What your teams do with this module
Real use cases reported by our IFS clients in production.
Updating 500 purchase items
The procurement team exports the items, updates supplier prices and lead times in Excel, then reimports. Fully autonomous — no IT ticket required.
Loading the chart of accounts
At the start of the fiscal year, the controller loads the new chart of accounts directly from Excel. Line-by-line validation — no incorrectly formatted account gets through.
Initializing IFS projects
The PMO exports the project template, fills it with the new project data, and loads it into IFS. Project structure and hierarchy created in minutes.
Your business teams become self-sufficient on IFS
Questions about this module
Everything you need to know about Excel import/export to IFS with ERP Control.
ERP Control supports import and export of all tables exposed via the IFS ODATA API. Reference data tables (items, suppliers, customers, project structures, chart of accounts, etc.) are the most common use cases. If a table is accessible via ODATA, it can be imported.
Each row is processed independently. Valid rows are imported into IFS; error rows are flagged with a precise message. You can choose to skip the errors and import the rest, or fix them first and relaunch. The entire file is never rejected as a whole.
No. The mapping module guides you in matching your Excel columns to IFS fields. You can start from any existing Excel file — an export from another system, a file prepared by your team, or the template generated by ERP Control during a previous export. The mapping is saved for future imports.
Yes. The multi-table export allows you to include a main table and its related sub-tables in a single structured Excel file — for example, order headers with their lines. Each table is exported to a separate tab, with relationships preserved to facilitate reimport.
Yes, fundamentally. The IFS Data Migration Tool is designed for initial data migrations during a deployment — it requires a technical profile and knowledge of IFS internal structures. ERP Control Import/Export is designed for recurring reference data updates during day-to-day operations — usable by your business teams, without any technical profile. The two tools are complementary.
Ready to make your business teams self-sufficient on IFS?
2-week POC on your real data. First import in a few hours. Zero client-side installation.