by Help Desk Migrationfor Jira Cloud and Jira Server 7.0.0 - 8.2.6
    Supported
    Help Desk Migration supports this app.

    Get support

    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Supported
    Help Desk Migration supports this app.

    Get support

    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Unsupported
    Jira Service Desk
    This app is compatible with Jira Service Desk.

    A complete migration solution to move from Samanage to Jira Service Desk

    A complete migration solution to move from Samanage to Jira Service Desk

    A complete migration solution to move from Samanage to Jira Service Desk

    Get started in minutes

    Migrate custom fields

    Run a free test

    You don'r need to be an expert to use the tool. All it takes to get started is connect your source and target service desks.

    Other than migrating incidents, users and requesters, our service also migrates default and custom fields. That way, letting you keep every bit of important information.

    To make sure that the data migrates correctly, we offer you a Free Trial. The process includes 20 tickets and all related data. In a matter of minutes, you will see a small portion of your data in Jira Service Desk.

    Get started in minutes

    Migrate custom fields

    Run a free test

    You don'r need to be an expert to use the tool. All it takes to get started is connect your source and target service desks.

    Other than migrating incidents, users and requesters, our service also migrates default and custom fields. That way, letting you keep every bit of important information.

    To make sure that the data migrates correctly, we offer you a Free Trial. The process includes 20 tickets and all related data. In a matter of minutes, you will see a small portion of your data in Jira Service Desk.

    More details

    WHAT YOU MAY MIGRATE AUTOMATICALLY

    • Tickets
    • Contacts
    • Users
    • Attachments
    • Public Notes
    • Custom fields

    Also you can use Custom Migration Service in case you have specific migration requirements.

    PLATFORMS THAT ARE ALSO SUPPORTED FOR MIGRATION FROM

    • Zendesk
    • Freshservice
    • Desk.com
    • Kayako
    • LiveAgent
    • Zoho Desk
    • Help Scout
    • Groove
    • Helpshift

    OUR BENEFITS

    • Free Demo Migration
    • Custom fields migration
    • Preserving relations between objects
    • Easy to change fields mapping (if you want to)
    • Automated process

    More details

    WHAT YOU MAY MIGRATE AUTOMATICALLY

    • Tickets
    • Contacts
    • Users
    • Attachments
    • Public Notes
    • Custom fields

    Also you can use Custom Migration Service in case you have specific migration requirements.

    PLATFORMS THAT ARE ALSO SUPPORTED FOR MIGRATION FROM

    • Zendesk
    • Freshservice
    • Desk.com
    • Kayako
    • LiveAgent
    • Zoho Desk
    • Help Scout
    • Groove
    • Helpshift

    OUR BENEFITS

    • Free Demo Migration
    • Custom fields migration
    • Preserving relations between objects
    • Easy to change fields mapping (if you want to)
    • Automated process

    Reviews for cloud

    (0)Sign in to write a review

    There are no reviews yet. Be the first to review this app.

    Reviews for server

    (0)Sign in to write a review

    There are no reviews yet. Be the first to review this app.

    Reviews for Data Center

    (0)Sign in to write a review

    There are no reviews yet. Be the first to review this app.

    Cloud Pricing

    Server Pricing

    Data Center Pricing

    This app is sold by a third-party vendor.

    Let us know that you'd like to manage this app's billing on your Atlassian invoice.

    This app is sold by a third-party vendor.

    Contact the vendor to evaluate or purchase this app.

    Pricing FAQ

    What does 'paid-via-vendor' mean?

    Paid-via-vendor apps are licensed and purchased directly through the vendor who makes this app.

    Payment for paid-via-vendor apps is not handled by Atlassian.

    Will paid-via-vendor transactions be on my Atlassian invoice?

    Paid-via-vendor transactions are not managed by Atlassian. This means transactions for paid-via-vendor apps will not be on your Atlassian invoice.

    Pricing FAQ

    What does 'paid-via-vendor' mean?

    Paid-via-vendor apps are licensed and purchased directly through the vendor who makes this app.

    Payment for paid-via-vendor apps is not handled by Atlassian.

    Will paid-via-vendor transactions be on my Atlassian invoice?

    Paid-via-vendor transactions are not managed by Atlassian. This means transactions for paid-via-vendor apps will not be on your Atlassian invoice.

    Help Desk Migration provides support for this app.

    Help Desk Migration provides support for this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Versions

    Jira Cloud Released 2019-03-14

    Summary

    Solarwinds Service Desk (formerly Samanage) to Jira Service Desk

    Versions

    Version 1.0.0 Jira Server 7.0.0 - 8.2.6 Released 2019-03-14

    Summary

    Solarwinds Service Desk (formerly Samanage) to Jira Service Desk

    Installation

    • Connect Solarwinds/Samanage and Jira Service Desk accounts. Select Solarwinds/Samanage from the drop-down menu and provide access credentials. Select Jira Service Desk as your new platform and provide your access credentials.
    • Select objects you want to migrate between SolarWinds (Samanage) and Jira Service Desk. Then click the "Map fields" button to match up ticket fields.
    • Map the fields you had in SolarWinds and fields in Jira Service Desk. Note that if you want to migrate custom fields to Jira Service Desk, you need to create them in the target project before starting the migration.
    • When you're done with the mapping, you can begin the Free Demo Migration. This step is necessary to check if the data migrates correctly. Once the process is complete, download the file generated by the Migration Wizard and upload it to Jira Service Desk. That way, you will import a small portion of the tickets. Carefully check the result and either continue your data migration or contact our team in case of any questions.
    • Connect Solarwinds/Samanage and Jira Service Desk accounts. Select Solarwinds/Samanage from the drop-down menu and provide access credentials. Select Jira Service Desk as your new platform and provide your access credentials.
    • Select objects you want to migrate between SolarWinds (Samanage) and Jira Service Desk. Then click the "Map fields" button to match up ticket fields.
    • Map the fields you had in SolarWinds and fields in Jira Service Desk. Note that if you want to migrate custom fields to Jira Service Desk, you need to create them in the target project before starting the migration.
    • When you're done with the mapping, you can begin the Free Demo Migration. This step is necessary to check if the data migrates correctly. Once the process is complete, download the file generated by the Migration Wizard and upload it to Jira Service Desk. That way, you will import a small portion of the tickets. Carefully check the result and either continue your data migration or contact our team in case of any questions.

    Similar apps