Your IFS customizations migrate
automatically. Nothing gets lost.
IFS Lobby, datasources, projections, report layouts — everything is migrated across environments via structured, tracked, and auditable CRIM projects. Zero manual recreation.
migrated
recreation
project statuses
audit log
IFS customizations are the most overlooked part of every project
Every IFS project generates customizations — lobby, datasources, reports, projections. These objects cannot be migrated via standard tools. The result: your teams recreate them manually from one environment to the next, hoping nothing gets missed.
It's time-consuming, error-prone, and completely untracked. If an auditor asks what was migrated during a go-live, you have no formal answer.
An industrialized CRIM migration, end to end
From draft project to archived delivery — every step is structured, tracked, and auditable.
Structured CRIM projects
Each migration is organized as a CRIM project with a full lifecycle: draft → active → delivered → archived. You always know exactly where each migration stands.
Precise CRIM tags per object
Each IFS object is tagged with its precise CRIM identifier. Instantly find which project each customization belongs to, and in which environment it exists.
Object-by-object comparison
Before each migration, visualize field-by-field differences (JSON diff) between the source and target object. No surprises at execution time.
Real-time streaming migration
Migration runs with real-time tracking via Server-Sent Events. You see each processed object appear as it happens — no more waiting in the dark.
Immutable audit log
Every action is recorded with IP address, username, and before/after state. The log is immutable — it cannot be modified or deleted.
11 IFS object types covered
Workflows, page configurations, data sources, lobby elements, home pages, reports and layouts, entities, projections, active projections, events and event actions — full coverage of your IFS customizations.
From draft to archive — every step is controlled
A CRIM project can only move forward by following its lifecycle. No migration reaches production without going through the validation steps.
Draft
Identification and listing of objects to migrate. Defining the scope of the CRIM project.
Active
Migration in progress. Comparison, streaming execution, and real-time tracking of each object.
Delivered
Migration validated by the project owner. All objects are in place in the target environment.
Archived
Project closed and retained in history. Accessible at any time for audit or reference.
What it changes for your IFS project managers
Questions about this module
Everything you need to know about IFS customization migration with ERP Control.
CRIM stands for Custom Report, Interface, and Modification — the IFS customizations. In ERP Control, this term covers all objects created or modified in IFS during a project: user profiles, datasources, lobby elements, custom entities, projections, and report layouts.
Yes. ERP Control handles the migration of IFS lobby elements via the standard API. The different component types (widgets, menus, shortcuts, dashboards) are supported within the scope of objects exposed by the IFS ODATA API.
The JSON diff comparison performed before migration shows you exactly what differs. If the object already exists in the target, you can choose to update it or skip it. No automatic overwrite without your explicit consent.
Yes. The audit log is immutable and retained indefinitely, even after the CRIM project is archived. You can access the full history at any time — who migrated what, when, with what result, from which IP.
Absolutely — and it is even the recommended combination for IFS go-lives. The Promotion module handles functional configuration tables; the CRIM module handles customizations. Together, they cover all objects to be migrated during an IFS go-live.
Ready to industrialize your CRIM migrations?
2-week POC on your real data. IFS connection in less than a day. Zero client-side installation.