Core TSIs : Migration to Activity planner : Required tasks before migration
Required tasks before migration
Before executing the migration, complete the following tasks:
Action
Remarks
Instructions
Close or end maintenance plans that need not be migrated.
Plans with an end date before the migration date and with a status Closed are not migrated.
In the Maintenance Planner TSI, ensure that any plan that must not be migrated is set to Closed or has an end date earlier than the migration date.
PPM Profiles
PPM order generation should not run during migration
In the Maintenance Planner TSI, stop all scheduled profiles.
Postpone scheduled tasks for order generation
Orders generated during the migration may not be migrated. Generating new planned activities during migration can interfere with the migration process.
In the Scheduled Tasks TSI, disable the following scheduled task(s):
• sysppm_scheduled_profiles (order generation from maintenance planner)
• sys_activity_ppm_profiles (order generation from activity planner)
• sys_generate_plannedactivities
A task can be postponed by changing the schedule. Example; change the schedule to ‘1 month’.
* 
Write down the original value, to be able to update to the original value after migration.
Postpone schedule for scheduled cleaning tasks SYSEVENTLOG_CLEANER and SYSBACKGROUND_ACTION_CLEANER
The migration creates log messages in the event log and triggers background actions.
It is recommended to temporarily prevent cleaning of these business objects until the migration is fully executed and the migration log is downloaded.
In the TSI Scheduled tasks change the schedule of SYSEVENTLOG_CLEANER and SYSBACKGROUND_ACTION_CLEANER, so that is not executed until after migration is finished. Example; change the schedule to ‘1 month’.
* 
Write down the original value, to be able to update to the original value after migration.
Disable TMS
Consider disabling any TMS that creates or changes Maintenance activity definitions or PPM orders.
Postpone active synchronization with the data lake
To optimize performance and prevent unnecessary synchronization during migration, pause the connection to the data lake temporarily. Restart synchronization after migration to synchronize all new activities and details.
Create a backup
After configuring AMM 3.0 and before starting the migration, create a backup.