Skip to main content
Question

Best practice for grouping migration jobs and promoting to Prod – IFS Cloud 2025 R2

  • March 15, 2026
  • 1 reply
  • 47 views

Hi all,

In IFS Cloud 2025 R2, we have multiple data migration jobs that need to run together.

Is there a recommended way to group these jobs and trigger them once instead of running them individually?

Also, what is the best practice to move migration jobs and related data from Customer QA to Production?

Thanks!

1 reply

martin.surasky
Sidekick (Customer)
Forum|alt.badge.img+9
  • Sidekick (Customer)
  • March 15, 2026

Hello ​@chandra sekhar 

 

If you have multiple data migration jobs that need to run together, you have to learn to use the MIGRATE_SOURCE_DATA Migration Job and the Intface_Header_API.Start_Job (or the Intface_Header_API.Start_Job_From_Server, which is similar) Procedure Names.

 

From IFS Documentation:

Intface_Header_API.Start_Job: This will start another job before the main loop in this job is executed. To specify the name of the job to be started, you must use RMB 'Method List Attribute..' and enter the Job ID in column 'FixedValue' for column INTFACE_NAME. This method does not return info about success or failure, and the main job will continue even if an error occurred on the first job.

Intface_Header_API.Start_Job_From_Server: Setup is the same as above. This procedure returns info about failure, and will stop any further processing if any errors occurred.

 

More info here: https://docs.ifs.com/techdocs/23r2/030_administration/050_data_management/050_data_migration/010_data_migration/040_method_list/

 

If you want a working example and you have access to a recent build of IFS Cloud, look for the 002_FLM_AC_RUN_ALL. This job (pre-installed in IFS) does precisely that. It runs many migration jobs (such as 100_FLM_AC_ASSEMBLY, 200_FLM_AC_SYSTEM, 220_FLM_AC_SUB_SYSTEM, etc).

 

As far as moving from one environment to another, you probably should use the FNDMIG_EXPORT and FNDMIG_IMPORT. They are very simple to use. You will find a pre-installed job using this procedure. Read the comments on the job header.

 

Hope that helps!