Migrate from Space to SpaceCode
This guide will help you safely transit from Space to SpaceCode without compromising your data and work processes. In case you’re not considering switching to SpaceCode, please read Migrate from Space to Alternative Software instead.
SpaceCode can be considered a simplified version of Space with an improved user interface designed around its core features — Git hosting and code reviews. Other important Space subsystems that may have been part of your development cycle, such as Automation CI/CD and Issue tracking, will be only available in the form of integration with comparable JetBrains tools. The rest of Space features will be discontinued with data saving options provided.
What will stay in SpaceCode
Most of your core Space entities, processes and configurations will not be affected or interrupted when you switch to SpaceCode — you and your team will be able to continue working as before. The following will stay intact:
Your repositories and commit history.
All repository related settings and configurations.
Code review and merge request history, including assignments, comments and timeline notifications.
Quality Control settings (i.e. push and merge restrictions, Quality Gates, Safe Merge, etc.)
User access permissions, memberships, roles — on both organization and project levels.
User profiles, credentials, authentication and authorization settings.
Open HTTP API with API Playground.
iOS and Android apps, a desktop app, and IDE plugin will reflect functionality changes.
What will NOT stay in SpaceCode
Automation. You will be able to convert and transfer your Automation jobs to JetBrains TeamCity and continue using them for your CI/CD needs.
Issues. You will be able to move your issues to an alternative planning tool — JetBrains YouTrack.
Documents. Project documents can be exported to YouTrack Knowledge Base.
Checklists. Can be extracted via HTTP API.
Blog posts. Can be extracted via HTTP API.
Chats. Messages can be retrieved in batch via HTTP API.
Packages. Package repository source data can be accessed and retrieved via HTTP API.
Calendars and calendar events such as Meetings, Absences, Holidays. Personal calendars can be exported to
.ICSfiles.To-do lists.
Locations.
Work schedule.
Availability status.
Transition Steps
Step 1. Try SpaceCode
Start by familiarizing yourself with the new SpaceCode UI. You and your teammates can switch to SpaceCode directly from your Space interface and easily switch back if you wish.
If you're using Space On-Premises, upgrade your instance to the latest version 2024.2.2. You won't be able to switch to SpaceCode without upgrading first.
To switch to the new SpaceCode interface, just click Try SpaceCode.
You'll be redirected to a new address:
[your-organization-name].jetbrains.space/code
which is a different entry point for your instance. Note the appended /code at the end of the URL. Your old Space UI is still accessible at the original address:
[your-organization-name].jetbrains.space.
You can easily switch back by navigating to the original URL.
Step 2. Enable redirect
In your new SpaceCode UI, you'll be offered the option to Enable Redirect. This will automatically redirect you to SpaceCode whenever you navigate to repository or code review features using the old address. You will still be able to access deprecated features that are no longer available in SpaceCode, such as Issues and Documents, even with redirect enabled.
If for some reason you need to view the old version of repository and code review pages, you can disable the redirect:
On the top right, click your avatar and choose Preferences.
On the left sidebar menu choose Workspace and turn off Redirect to new UI.
Step 3. Migrate data and processes
Read this guide and follow the instructions to migrate your data and processes to TeamCity and YouTrack. Take it one step at a time to ensure a smooth transition.
Step 4. Switch your mobile app to SpaceCode
When you no longer need to use deprecated features, like Chats, To-do list, etc., on your iOS or Android device, you can switch your Space app to SpaceCode.
In order to do that, you need to log out of your Space app, and then log in again entering your new SpaceCode address [your-organization-name].jetbrains.space/code
You can also log into SpaceCode by scanning a new QR code which you can get from your SpaceCode web interface:
On top of the page, click Help.
Choose iOS app or Android app from the menu.
Click Next: Authorize with QR code.
Scan the QR code with your phone to log into SpaceCode.
Space Modules and Migration Options
Since Space is a complex platform composed of many subsystems (modules), the migration process is carried out on a module-by-module basis.
We’ll discuss each module separately, outlining available solutions and providing detailed instructions. If you only need to migrate or save data from certain modules, you may skip reading about the rest, but please keep in mind that some modules are tightly integrated, so it is advisable to at least familiarize yourself with all the options to prevent data loss and ensure smooth transition.
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 tracking and planning tool. 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 projects.
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.
After you have successfully transferred your issues to a YouTrack project, you can integrate it with SpaceCode to view issue snippets in commit messages and comments and to automatically close an issue when a relevant merge request is completed.
Option 2. 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 tested and well documented solution we can offer is a migration to JetBrains TeamCity — a comprehensive and robust 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.
See YouTrack migration instruction.
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 archived 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.