How To Migrate Your Existing Apps

When upgrading from one version of the Vuforia Engine release to the next, it's recommended that you follow the practices defined in the migration guide for your SDK version. This article identifies both API and project structure changes to the SDK that you should be aware of when upgrading a project from a prior version of the Vuforia Engine Platform.

Migrating from Vuforia Engine 7.x to 7.2

Unity developers looking to migrate to Vuforia Engine 7.2 should follow the steps described in How to Migrate a Unity Project document.

Native developers looking to migrate to Vuforia Engine 7.2 should follow the steps described in How to Migrate to Vuforia Engine 7.2 document

Migrating from Vuforia 6.2 to 6.5

Starting with Vuforia Engine 6.5, Vuforia's Untiy support is being improved. Vuforia Engine is integrated into Unity 2017.2 or later. Unity developers need to migrate their 6.2 projects to 6.5. Native developers do not need to migrate their C++ / Java projects.

Migrating from Vuforia Engine 5 to 6

The What's New in Vuforia Engine 6 article describes new features and APIs that have been introduced to support Windows UWP builds, a new Advanced Camera API, and the VuMark. These changes will not affect the migration of Vuforia projects that use the Java and C++ APIs.

Be sure to review the migration guides for prior versions of the SDK if migrating from an earlier SDK version to Vuforia Engine 6. You'll may need to migrate to an interim version before applying any migration steps for the current version of the SDK.

Migrating from Vuforia Engine 4 to 5

The What's New in Vuforia Engine 5 article describes new APIs that have been introduced to support digital eyewear and the ability to call Trackable states introduced with Vuforia Engine 5. These changes will not affect the migration of Vuforia projects that use the Java and C++ APIs.

There has been a refactoring of the Unity APIs and SDK folder structure that will require modifications to Unity projects that are migrated to Vuforia Engine 5.

Apps developed with the Vuforia Engine 4 Digital Eyewear Beta SDK will need a new license key if they were developed for video see-through eyewear.

Migrating from Vuforia Engine 3 to 4

Vuforia Engine 4.0 introduced a few significant changes to the Vuforia API. What's New in Vuforia Engine 4 provides details on how to transition your existing code to Vuforia 4.0.

1. All Vuforia Engine 4.0 apps need to implement a unique license key from the Vuforia License Manager.
2. The ImageTracker class has been replaced with the ObjectTracker as a unified Tracker type for both objects and images.
3. The Smart Terrain API utilizes a new command design pattern which relies on a SmartTerrainBuilder class that manages the Reconstructions created by Smart Terrain.
4. A new 'Vuforia' namespace has been introduced for Unity. You need to add the following to the top any C# scripts that reference the Vuforia API.

Further Migration Information

Following documents provide more information on platfrom specific migration issues: