Select your language
Leveraging the Smart Data Manager to transform legacy chaos into structured, audit-ready assets.
In the 25R2 release, data migration has evolved from a technical "backend task" to a governed business process. With the enhanced **Data Migration Manager (DMM)**, IFS Cloud now offers a standardized, containerized approach to moving data, significantly reducing the reliance on fragile, custom PL/SQL scripts.
The core innovation in 25R2 is the maturity of the Smart Data Manager. Unlike legacy migration tools that pushed data directly into production tables, the Smart Data Manager utilizes a strict "Staging" methodology. This ensures that no data enters the core system until it passes rigorous validation rules defined by the business, not just the IT department.
25R2 allows you to create isolated "Migration Projects" (Containers). You can load data from Excel, CSV, or external SQL DBs into these containers without affecting the live environment. This allows for iterative testing—you can wipe and reload the container 50 times without creating "junk" in the actual Master Data.
The Mapping tool in 25R2 provides a visual interface to map Legacy Fields to IFS Cloud Fields.
New in 25R2 Auto-Mapping: The system uses fuzzy logic to suggest mappings based on column headers, speeding up the initial setup by up to 40%.
The system runs "Basic Data" checks before the load. For example, if you try to migrate a Customer Order, the Smart Data Manager verifies that the Customer ID, Sales Part, and Currency already exist in the target environment. If not, the specific line is flagged as "Error" while valid lines proceed.
Migration jobs built in 25R2 are persistent. Unlike one-off scripts, these migration containers can be reused for future M&A activities (merging new companies) or bulk-updates, ensuring your investment in data mapping pays dividends long after Go-Live.
Do not attempt to use old IFS Applications 9/10 "FNDMIG" scripts directly in IFS Cloud 25R2. The API structures and REST endpoints have changed. 25R2 requires utilizing the Deployment Containers for stability.
