---
title: "Automated script migration"
canonical: "https://support.appfire.com/space/PSJ/1518928088/Automated%20script%20migration"
format: markdown
---
> Macro (aura-html)
The table below outlines the steps to perform automated script migration using a tool such as [Jira Cloud Migration Assistant](https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant?tab=overview&hosting=datacenter) (JCMA) or [Configuration Manager for Jira](https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira-cmj?hosting=cloud&tab=overview) (CMJ).
| **Step 1: Migrate the Jira instance using a tool ** | 1. Update the sil.aliases properties file. For details, see [SIL aliases](https://appfire.atlassian.net/wiki/spaces/PSJC/pages/496206057).
2. Search code for hard-coded custom field IDs.
3. Convert hard-coded custom field IDs to aliases. |
| --- | --- |
| **Step 2: Validate ****post function and Listener ****scripts** | Starting with the post function and listener script types will quickly expose potential major issues. These scripts are more likely to contain project names, issue type names, and other configuration-specific elements that may need to be resolved. Early identification of discrepancies in these names lets you minimize the impact on the project and resolve potential issues that require Jira changes.
1. In SIL Manager, run the syntax check on each script to validate the code.
2. If you discover any name conflicts, use find/replace to search for similar issues across all scripts. |
| **Step 3: ****Validate Scheduler scripts, Webhooks, SIL Panel, and SIL Runner Gadget scripts** | Scripts of these types should migrate easily. Any major issues would have been caught and resolved earlier in the process.
1. In SIL Manager, run the syntax check on each script to validate the code.
2. If you discover any name conflicts, use find/replace to search for similar issues across all scripts. |
| **Step 4: Convert ****Mail handler**** scripts ** | The changes required by mail handler scripts are minor and this conversion effort should be minimal.
For details, see [the Mail handler scripts section](https://appfire.atlassian.net/wiki/spaces/PSJ/pages/edit-v2/1519616224#Mail-handler-scripts). |
| **Step 5: Convert JQL function scripts** | Due to the nature of the changes, JQL scripts require more extensive updates than other script types during migration. SIL provides utility scripts that can help with JQL-related migration in two ways:
- To scan your existing JQL filters and identify where DC keywords are used that won't work in Jira Cloud.
- To automatically update those JQL filters to use the Cloud-compatible keywords.
For details, see [the Scripted JQL functions/keywords section](https://appfire.atlassian.net/wiki/spaces/PSJ/pages/edit-v2/1519616224#Scripted-JQL-functions%2Fkeywords). |
| **Step 6: Convert Live Fields scripts** | Live Fields in Jira Cloud uses JavaScript and Atlassian APIs, unlike Data Center, which uses SIL. The cloud version of Live Fields has more limited functionality than the Data Center version. Converting these scripts requires significant work, including developing workarounds where Cloud features are missing.
For details, see [the Live Fields section](https://appfire.atlassian.net/wiki/spaces/PSJ/pages/edit-v2/1519616224#Live-Fields-scripts). |