Manual Migration Tools

Introduction

This guide provides step-by-step instructions for migrating from Attach File for Jira Server/Datacenter to Attach File Cloud.

By following these instructions, you can seamlessly transition your attachment management system between these two environments.


1.Prerequisites

Before starting the migration process, ensure that you have the following prerequisites:

  • Access to both the Attach File for Jira Datacenter and Attach File Server environments.
  • Administrative privileges in both Jira instances.


2.Attachments organization

  • Navigate to the location where you stored your attachments in Attach File for Jira Datacenter.

           For example: C:\Users\pc\Atlassian\Application Data\Jira 9.9.2\data\attachments\kepler-attach-file.

  • Alternatively, use the Jira view issue interface to manually upload each attachment file.
  • Follow the prompts to select the appropriate project, issue, or custom field for each attachment upload.
  • After uploading, open your Jira instance.
  • Navigate to the desired project and select "Issues" to view the issue screen.
  • In the view issue screen, you can see attachments associated with each issue.
  • Regroup your attached files based on the projects they belong to.
  • For each project, create a new folder and name it with your project key to organize the attachments accordingly.
  • Inside each project folder, create subfolders for individual issues key to further group the files based on the issue key they belong to.
  • After regrouping your files by project and issues, open your Jira Cloud instance.
  • Navigate to the field configuration section.


3.Install Kepler – Attachment Fields | Simple, Multiple for Jira Cloud

  • Navigate to the Atlassian Marketplace by visiting Atlassian Marketplace.
  • Search for "Attach Kepler - Attachment Fields | Simple Multiple" in the marketplace search bar.
  • Select the plugin from the search results to open its details page.
  • Click on the "Get it now" or "Try it free" button to initiate the installation process.
  • Log in to your Atlassian account if prompted and choose the Jira Cloud instance where you want to install the plugin.


4.Plugin Configuration

  • To configure the plugin, navigate to the navigation bar dropdown menu in your Jira Cloud instance.
  • From the dropdown menu, select "Kepler Attachment Fields Cloud Config" to access the plugin configuration page.
  • On the configuration page, users can choose the default Kepler storage location for their files. Additionally, users have the option to store files in an external storage by creating an SFTP (Secure File Transfer Protocol) connection. Configure the desired settings based on your requirements and preferences.
  • Save the changes to apply the configuration settings.
  • After accessing the plugin configuration page as described in previous point, navigate to the section for creating Attachment Fields. Here, you can specify the details for each Attachment Field, including the Custom Field Name, File Max Size, Attachment Type (Simple or Multiple), whether to compress files, allowed file extensions, Supported Project Keys, and Associated Issue Type ID.
  • Once all the details are entered for each Attachment Field, click on the "Save" button to save the configuration.
  • Repeat these steps for each Attachment Field you wish to create, ensuring alignment with the project folders created in step 2 (Attachment organization).

 

5.Migrating and uploading attachments

  • In the final step, go to the view issue page in Jira Cloud.
  • Click on "Upload Files" and navigate to the folder organized by projects and issues created in step 2. Within this folder structure, you'll find your files neatly grouped according to the projects and their respective issues. Select the desired files and proceed with the upload process.


Conclusion

In summary, this guide has outlined the steps for migrating from Kepler Attachment Fields for Jira Datacenter to Kepler Attachment Fields Cloud.

For more details on using the plugin, please refer to the documentation. If you have any questions, our support team is here to help!