I. Migration Checklist

The migration checklist is shown below. The actual scope depends on the options you select.

图1

II. Data Usage Notes

The following table provides a feature mapping for reference. You can open the linked user guide for details.

III. FAQ

1. The import times out.
   Check whether Apache or Nginx resources are insufficient, and tune the server configuration as needed.
2. Descriptions look different after import.
   The Sanplex editor supports text, images, and links. Other formats are converted into HTML-rendered content.
3. There are fewer fields than in Jira.
   Only fields that contain data are imported. Unused fields are not imported; you can add them in Workflow. Additionally, depending on your product edition, custom fields may be limited.
4. An extra iteration with the same name appears under a project.
   If some issues have an empty Sprint/Iteration value, the system automatically creates an iteration with the same name as the project to hold those issues.
5. When importing from files, Save shows “Cannot connect to API”.
   The domain may be incorrect (for example, an IP address was used), or API authentication may not be enabled.
6. User permissions were not imported.
   Jira and Sanplex permission models differ significantly. Reconfigure permission groups after import.
7. Accounts cannot log in.
   Sanplex usernames do not support special characters other than underscores. For cloud migrations, if the username is unusual, use the email address as the username.
8. Field formats differ after import.
   If you map to an existing field, only data is imported and the field format remains unchanged. If you create a new field, the format may be normalized based on whether options exist (for example, single-line text or single-select dropdown), subject to Workflow-supported field types.
9. History is not displayed.
   History is not migrated at this time.
10. Story Points are missing.
    The Story Points field must be mapped manually.
11. Imported actions are not visible.
    Imported actions are disabled by default. Enable them in Workflow to use them.
12. User count exceeds the license.
    If the user count exceeds the licensed limit, import will stop and users may be unable to log in. Contact us to expand your license capacity.
13. Multiple “Requirement/Task/Bug” options appear during object mapping.
    For Jira Cloud team-managed projects, the IDs of requirement/task/bug differ from system defaults, and both will be detected.
14. Import error: SQLSTATE[42000] ... 1118 Row size too large ...
    Before importing, run SET GLOBAL innodb_strict_mode = OFF; on the database, then retry the import.
15. Other issues
    Contact us for assistance.