Catalog
I. Migration Checklist
| Type | Jira | Sanplex | Migration | Notes |
|---|---|---|---|---|
| User management | Users | Admin > Users | Automatic | Usernames and email addresses are migrated. |
| Groups | Admin > Users | Manual | Jira handles permissions very differently, so permission groups have to be set up again in Sanplex. | |
| Notifications | Notification settings | Admin > Notifications | Manual | Notifications work very differently in the two systems, so notification settings have to be set up again in Sanplex. |
| Automation | Automation | Rule engine | Manual | Automation works differently in Sanplex, so rules have to be built again. |
| Jira project data | Project name | Project name | Automatic | |
| Project lead | Project manager | Automatic | ||
| Project type | Project type | Automatic | All Jira projects are imported as product-type agile projects. | |
| Project roles | Project > Settings > Team | Manual | Team members have to be set up again after the import. | |
| Project members | Project > Settings > Team | Automatic | ||
| Sprint | Execution | Automatic | If a story or task has no sprint, it is automatically placed in a sprint named after the project. | |
| Release | Release | Automatic | It becomes a release after the import, and a build of the same name is created. | |
| Jira project configuration | Issue type scheme | Workflow > Project Flow | Automatic | An unarchived project automatically gets its own project workflow template after migration, and the configuration is read from that template. |
| Field configuration | Workflow > Project Flow | Partial | Attributes of fields in use are synced, and unsupported formats fall back to a compatible one. Default values and required-field settings can't be migrated yet. | |
| Issue type screen scheme | Workflow > Project Flow | Manual | Set it up again in Sanplex after the import. | |
| Workflow configuration | Workflow > Project Flow | Automatic | Workflow statuses and steps are migrated; triggers, conditions, validators, and post functions aren't supported yet. | |
| Permission schemes | Project > Settings > Permission | Manual | Jira handles permissions very differently, so permission groups have to be set up again in Sanplex. | |
| Jira issue configuration | Issue type | Workflow > Objects | Automatic | Depending on your choice during the import, it syncs to a built-in object or to a newly added one. |
| Field | Workflow > Fields | Automatic | Built-in fields and custom fields that contain data are synced to built-in fields or to a newly added object, depending on your choice during the import. | |
| Statuses | Workflow > Statuses | Automatic | Depending on your choice during the import, statuses sync to the built-in statuses or to those of a newly added object. | |
| Priorities | Admin > Features > Priorities | Automatic | Synced automatically; in Sanplex, priorities can differ from one object to another. | |
| Issue linking | Admin > Features > Relation | Automatic | Depending on your choice during the import, links sync to the built-in relation or to a newly added one. | |
| Resolution | Admin > Features | Automatic | Maps to the resolution of bugs and the closed reason of stories, tasks, feedback, and tickets in Sanplex. | |
| Jira issue data | ID | ID | Automatic | |
| Project | Project | Automatic | ||
| Issue type | Automatic | Different issue types are imported as different objects in Sanplex. | ||
| Summary | Title | Automatic | ||
| Status | Status | Automatic | ||
| Priority | Priority | Automatic | ||
| Sprint | Execution | Partial | Newly added objects belong to the project but don't include the Sprint field. | |
| Description | Description | Automatic | ||
| Fix versions | Linked release | Partial | Shown only under the matching release and only for child stories and bugs; for other issues this field isn't imported. | |
| Resolution | Closed reason / Resolution | Automatic | Maps to the resolution of bugs and the closed reason of stories, tasks, feedback, and tickets in Sanplex. | |
| Creator | Created by | Automatic | ||
| Assignee | Assigned to | Automatic | ||
| Reporter | Reported by | Automatic | Added automatically. | |
| Watchers | Watchers | Automatic | Added automatically. | |
| Created date | Created on | Automatic | ||
| Date updated | Updated on | Automatic | Added automatically. | |
| Due date | Deadline | Automatic | Added automatically. | |
| Attachments | Attachments | Automatic | ||
| Linked issues | Linked objects | Automatic | ||
| Sub-tasks | Child objects | Partial | Stories and tasks support parent-child hierarchies; for other objects the relation is recorded and can be viewed under Linked relations. | |
| Activity > Comments | History > Comments | Automatic | ||
| Estimated / logged hours | Estimated / Cost hours | Partial | Built-in objects support both hour values and worklogs; newly added objects support hour values only. | |
| Custom fields | Custom fields | Automatic |
II. Data Usage Notes
The feature comparison is shown below. Click the user guides links to read the details.
III. FAQ
1. Data import times out
Check whether Apache or Nginx on your server is running short of resources, and adjust the configuration if it is.
2. The description format changes after import
The Sanplex editor only supports text, images, and links. Anything else is converted into HTML-rendered content.
3. Fewer fields appear after import than in Jira
Only fields that have actually been used are imported; unused fields are skipped. You can add the missing fields yourself in the workflow.
This can also be a matter of edition: the open-source edition only supports built-in fields, not custom ones.
4. An extra sprint with the same name appears under the project after import
If any issues under the project have no sprint, Sanplex automatically creates a sprint named after the project and puts those issues in it.
5. When importing a file, saving reports that the API can't be reached
The domain you entered may be wrong — for example, an IP address was used instead. It's also possible that authentication for API calls isn't enabled.
6. User permissions aren't carried over
Jira and Sanplex handle permissions very differently, so you'll need to set up permission groups again.
7. An account can't sign in
Sanplex account names don't support special characters other than the underscore. When migrating from a cloud edition, if an account name is unusual, you can use its email address as the username.
8. Field formats change after import
If you map to an existing field during import, only the data is imported and the format stays the same. If a new field is created, then apart from the formats that Sanplex workflows support, the field becomes a single-line text field or a single-select dropdown, depending on whether it has options.
Jira formulas can't be imported as Sanplex formulas either, so they have to be reconfigured after the import.
9. History isn't displayed
History isn't migrated at the moment.
10. Story points on stories aren't displayed
The story point field (Story Points) has to be mapped manually.
11. Actions aren't displayed after import
Imported actions are disabled by default. Enable them in the workflow if you want to use them.
12. The number of users exceeds your license
If the user count exceeds your license, the import stops and you can't sign in. Contact us to add more licensed users.
13. Several stories/tasks/bugs appear when matching objects
In Jira Cloud, the stories, tasks, and bugs of team-managed projects have IDs different from Sanplex's default stories, tasks, and bugs, so all of them are recognized.
14. Import fails with: SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs
Before importing, run the following in your database, then start the import again:
SET GLOBAL innodb_strict_mode = OFF
15. Problems importing data from the Jira plugin
Attachments from the Jira plugin aren't supported. Contact us if you need them imported and we'll handle it as a special case.
16. Other questions
Please contact us at [email protected].
