Since PIM 2.0 there are some "internal" jobs that have been added. There are created at the installation and must remain in the database. The problem is that the jobs are migrated by a MySQL dump that erase this internal jobs.
To keep this internal jobs, they have first to be installed. To do that I re-worked the destination PIM installation to execute the command "pim:installer:db" with the catalog fixtures "minimal". Then at the jobs migration step, the table "akeneo_batch_job_instance" is copied to keep the internal jobs, and they are re-inserted after the SQL dump.
Since PIM 2.0 there are some "internal" jobs that have been added. There are created at the installation and must remain in the database. The problem is that the jobs are migrated by a MySQL dump that erase this internal jobs.
To keep this internal jobs, they have first to be installed. To do that I re-worked the destination PIM installation to execute the command "pim:installer:db" with the catalog fixtures "minimal". Then at the jobs migration step, the table "akeneo_batch_job_instance" is copied to keep the internal jobs, and they are re-inserted after the SQL dump.