Skip to content

Migrate from Profinity V1 to V2

Profinity V2 is a significant architectural upgrade from V1, which ran on Windows only. It keeps the functionality of V1 and adds a web-based interface and an expanded API, but the two versions are not compatible. The incompatibilities are:

  • V2 profiles cannot be opened in V1.
  • V1 and V2 system configurations cannot be used by the other version.
  • The API structure and endpoints have changed significantly.

Migration has no downgrade path, so keep your V1 backups. To upgrade from Profinity 2.2 to Profinity 2.3, refer to Upgrade from Profinity 2.2.

Prohelion recommends a clean installation of V2, removing V1 before you install V2.

Before you begin, have the V2 installer for your platform, and administrator rights on the Windows computer for the V2 install. Uninstall V1 while signed in to Windows as the user account that V1 was installed under.

  1. Copy the V1 profiles, configuration files, CAN database (DBC) files, and any custom scripts or data to a location outside the V1 installation and its profile directory. Write down the component settings and addresses, and any custom V1 settings you want to replicate in V2.

  2. Check that every file you copied in step 1 is there and opens. Then uninstall V1 by running the V1 Windows installer and choosing its uninstall option, and remove the files in the V1 profile directory, Documents\Prohelion\Profinity.

    There is no downgrade path

    Keep your V1 backups.

  3. Install V2 as a new installation, not as an upgrade of V1, for your platform: Windows, Linux and macOS, or Docker. Confirm that V2 is running.

  4. Recreate the configuration. Create new profiles, add components in the V2 interface, upload each DBC file in the Upload DBC file (optional) setting of its Custom Component, and set the system settings for your environment.
  5. Check that every component is detected and configured correctly, and test the critical functions before you put the system into production.
  6. Review the security settings and user accounts, starting with the default administrator password described in the Security guide.

Get help

If something goes wrong during migration, check the installation page for your platform and the System configuration documentation. You can also contact Prohelion Support, or report the issue with the Feedback feature in Profinity.