Migrating Data From Other Version Control Systems

Zachariah Peterson
|  Created: July 28, 2022  |  Updated: November 23, 2022
MIGRATING DATA FROM OTHER VERSION CONTROL SYSTEMS

The development of electronic devices always involves the release of many different types of files. And these files are not static - they change as the project progresses. When filling a project with data, a user creates new files, modifies outdated files that have become irrelevant.

Managing project data is a separate task, especially for large developments where several participants with different specializations are involved in the process.

Traditionally, one way to manage data is to use a version control system such as Git or SVN (Subversion). They allow you to keep a detailed history of all changes and are suitable for collaborative work. However, the disadvantage of this approach is that these systems are general-purpose systems and do not take into account the specifics of electronics development.

Commit History:

Details of a separate commit:

Storage manager panel

Altium Designer has built-in support for version control systems. The Project panel displays the status of your files, as well as basic Git or SVN commands (such as update, commit, etc.).

The Storage Manager panel displays the full history of changes in your project files.

Project panel

Storage Manager panel

Why migrate to Altium 365?

Unlike other VCSs, Altium 365 is the system designed specifically for managing project data.

Here are some benefits:

  • You can always share a complete set of project data simply by providing a link;
  • Altium 365 provides advanced data sharing with MCAD systems;
  • You can share comments on the project with your colleagues in the form of notes directly in the Altium Designer environment and using web browser;
  • Altium 365 has a system of differentiation of user rights depending on the role;
  • Altium 365 is a constantly developing system which gives more and more possibilities for collaborative work on projects.

Moving to Altium 365

When you already have a workspace in Altium 365, nothing is easier than migrating your project with its history of changes and continuing to work in the Altium 365 environment, using all the advantages of the platform.

  • Once connected to the workspace, select Make Project Available Online from the context menu of the active project.
  • In the opened window, edit the project name (if necessary), select the location directory, and tick the Migrate to Altium 365 Versioned Storage checkbox. Click OK.

Note: the project name, description and placement directory can be changed later in the workspace.

  • After you click Migrate, Altium Designer will make some changes to the project file (with service information) and commit all the files to your current Git (or SVN) repository.
  • Commit history will show a commit with the following content.
  • The successful migration process will result in the window offering you to open your project in the workspace in the browser.

When you open the project for viewing in a web browser, you can verify the integrity of the migrated data. And change history is fully migrated from the version control system repository. From now on, you will work in the Altium 365 environment.

Important notices

  • The project is completely taken over by Altium 365 after migration, the connection with the old repository is no longer available;
  • When opening a project in an “old version” of repository (i.e. in the repository of an external version control system - on other PCs or other users), the user will be notified that it is necessary to migrate a local copy of the project to Altium 365 control. If the appropriate option (Update local project folder) is selected, this operation will be performed automatically;
  • If Do nothing is selected, the user will continue to work on the project under the external VCS. Such a project will have no connection to Altium 365.

Another cases

The project is in the Altium 365 workspace, but uses an external VCS.