Migrate from Space to Alternative Software
This guide will help you save your data or export it to other tools before you discontinue using Space. In case you’re considering switching to SpaceCode, please read the SpaceCode migration guide instead.
Given that Space is a complex platform composed of many subsystems (modules), the migration process is carried out on a module-by-module basis where specific procedures and options are available for each module. That said, the choices you make will depend on your unique usage background, the data stored, and the software you want to move to. That is why we urge you to read this guide thoroughly so you can weigh your options and come up with the best migration strategy that will ensure a trouble free transition and satisfying outcome.
Please note that while the migration options described in this guide have been tested and are recommended for their reliability and simplicity, you are not limited to them. Advanced users can set up their own migration procedures using Space API and Applications.
Space Modules and Migration Options
The following list gives you an overview of available migration options for each Space module. If you only need to migrate data from certain modules, you may skip reading about the rest. However, please note that some modules are tightly integrated, so it is advisable to familiarize yourself with all the solutions to get the complete picture.
Repositories and Git Hosting
If your repositories are hosted externally and mirrored by Space, there’s no need to do anything — you’re already set. But if your repositories are hosted internally by Space, all you need to do is create or update your local copy of the repository and then push it to a new remote location which you can set up with another hosting service of your choice, such as GitHub. This process doesn’t require any instructions on the Space end. Refer to your new hosting provider documentation.
Please note that while you can easily transfer your codebase and commit history, it is not possible to export repository settings, such as push and merge restrictions, Quality Gates, Safe Merge. The same applies to code reviews and merge requests, read more on them below.
Code Reviews and Merge Requests
As much as we’d like to, we cannot provide instructions for migrating your code review history to another Git hosting along with the repository as there’s no valid solution for that. However, you may consider saving the review messages as part of your Chat history which can be archived and downloaded. See Chats and Messages.
Issues (Issue Tracker)
Option 1. We provide a ready-to-use solution for migrating your Space issues to JetBrains YouTrack — a full-featured and widely adopted issue tracker. Both YouTrack Cloud or YouTrack Server are available.
The migration process is not overly complicated but may get time-consuming, primarily depending on the number of different fields and other entities currently configured for your Space issues.
Note: In addition to migrating the issues, you also have the option to export your project documents to YouTrack Knowledge Base as part of the same migration process (see Documents and Blogs).
To start migrating your issues to YouTrack, follow these step-by-step instructions.
Option 2. To migrate issues to other platforms (e.g. JIRA, GitHub), you can create your own script or application and use Space's dedicated HTTP API endpoint GET /api/http/projects/{project}/planning/issues to pull the data. (Open Space API playground and search for Get all issues.) This option requires advanced knowledge of both products’ APIs as no complete migration instructions are available.
Option 3. You can export issues to a .CSV or .XLSX file on a per-project basis.
Open the project and navigate to Issues.
On the top right click Reports and choose Issue list with a desired file format.
Automation (CI/CD)
At this point, the only well documented solution we can offer is a migration to JetBrains TeamCity — a robust and well known CI/CD server. You can choose between a cloud-based or on-premises instance.
While you’ll be able to convert Space Automation Jobs to TeamCity Build Chains preserving most of your configuration parameters, the process is neither straight-forward nor quick. Preparation and good knowledge of both products are required to ensure a smooth transition.
Documents and Blogs
Option 1. If you are going to adapt YouTrack as your issue tracker, you can export your Space project documents to YouTrack Knowledge Base using the same solution we provide for migrating your issues.
Please note that only text documents located in projects can be migrated to YouTrack. All other document types, such as personal documents, checklists, blog posts, cannot be migrated but can be retrieved and saved instead (see Option 2).
Option 2. You can export personal and project documents to .json files using a ready-to-run script.
Option 3. The following entities can be retrieved using respective GET requests to Space HTTP API which allows you to access most entities, provided you have necessary permissions.
Text documents
Published blog posts
Checklists
Uploaded files (.pdf, images, etc.)
Navigate to the API Playground to find endpoints and parameters.
Chats and Messages
Option 1. You can export channels and direct communications you are allowed to access to .json files using a ready-to-run script.
Option 2. Messages from public and personal channels can be also extracted using the dedicated Space HTTP API endpoint GET /api/http/chats/messages, provided you have necessary permissions. (For more information, open Space API playground and search for Get channel messages.)
Packages
Currently, we can’t offer a viable and well documented solution for migrating your packages elsewhere. The reason for this is that data formats and framework configurations vary greatly across different platforms, which creates a high risk of data corruption during the transition process.
That said, Space HTTP API allows you to access package repositories via GET /api/http/projects/{project}/packages/repositories/{repository}. For more information, go to the Space API playground and search for Get repository.
Should you decide to migrate your source data, please note that specific steps and tools required for exporting artifacts will vary depending on your destination and the types of artifacts being migrated. Some hosting providers offer built-in import tools you can utilize to transfer your data, while others may require running custom scripts or using third-party migration software.
Calendars
Personal calendars can be exported to .ICS files, a format recognisable by most calendar applications. To export your calendar:
Click your avatar and choose Calendar
On the top right, click the
Settings icon and choose Download as ICS file.