Migration Manager: Migrating Automation Script And Launchpoints

Body

Have you ever tried using Migration Manager to migrate Automation Scripts ? Had you noticed that even if you did everything correctly and successfully migrated the script there are no launchpoint data?

It's because out of the box, it doesn't automatically determine the two are related when you do the validation on a migration collection so it doesn't recommend adding the launch points. Thankfully, it's really easy to fix. In the Migration Collections application from the Select Action menu choose "Define Related Data and Lookup Rules". You link the AUTOSCRIPT table to the SCRIPTLAUNCHPOINT table so that when validation occurs it will know these are related and suggest adding them to your migration collection.

In the Migration Collections application from the Select Action menu choose "Define Related Data and Lookup Rules"

You would need to Create a New Rule:
Rule Name: AUTOLAUNCH
Primary Object: AUTOSCRIPT
Related Object: SCRIPTLAUNCHPOINT
Enabled: Checked
 
Related Columns:
Primary Column: AUTOSCRIPT
Related Column: AUTOSCRIPT

Now you would need to revalidate your collection and add the new relation to your collection.

1. After the validation is complete: Validation Results tab> Related
Configuration filter 'Related Object Structure' =DMLAUNCHPOINT

2. Select the result and click 'Add Related Configuration Entry to
Migration Collection'
3. Go Back to Migration Collection and verify that configuration is added.

4. Save>Create Package and Deploy as usual

Now you should be able to migrate your scripts and the launchpoint date associated with it.