> For the complete documentation index, see [llms.txt](https://multiset.gitbook.io/multiset/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://multiset.gitbook.io/multiset/workflow/migration-guide/vuforia-model-targets.md).

# Vuforia Model Targets

## Migration Guide: From Vuforia Model Targets to MultiSet Object Tracking

This document provides a comprehensive guide for developers transitioning their applications from Vuforia's Model Targets to the more advanced and robust MultiSet [Object Tracking](/multiset/basics/object-tracking.md) for object anchoring.

### Introduction

MultiSet Object Tracking is the direct equivalent of Vuforia's **Advanced Model Targets**. It is engineered for high-fidelity, 360-degree tracking of real-world objects using photorealistic 3D scans. Migrating to MultiSet offers significant advantages in performance, accuracy, and robustness.

#### Key Advantages of MultiSet Object Tracking

* **Superior Tracking:** Tracks objects from any angle using photorealistic scan data.
* **High Robustness:** Performs reliably in dynamic and challenging lighting conditions where other systems may fail.
* **Resilience:** Intelligently handles minor changes in an object's shape, texture, or appearance over time.
* **Seamless Workflow:** Allows you to reuse your existing 3D assets, ensuring a fast and efficient migration path.

***

### Migration Workflow

The migration process is designed to be as seamless as possible, leveraging your existing assets to preserve your development work. There is one primary workflow.

#### Step 1: Create an Object for Tracking using your Existing Scan File

You can use the exact same scan file (e.g., .glb) that you previously used to create your Vuforia Model Target dataset.

1. **Log In:** Access the [MultiSet Developer Portal](https://developer.multiset.ai/).
2. **Navigate to Object Tracking:** Select the "[Object Tracking](/multiset/basics/object-tracking.md)" section from the main dashboard.
3. **Upload Scan File:** Upload your photorealistic 3D model of the object (e.g., your .glb file).
4. [**Configure Tracking**](/multiset/basics/object-tracking/how-to-setup-a-object-tracking.md)**:** Choose the desired tracking type based on your object and use case.
5. **Activation:** Your Object will be processed and activated for use in your application within minutes.

#### Step 2: Integrate the MultiSet SDK in your Project

With your Object ready for tracking, you can now swap the SDK in your application. The following steps are for Unity, the most common development environment.

1. **Remove Vuforia SDK:** First, safely remove or disable the Vuforia Engine plugin and its associated scripts from your Unity project.
2. **Install** [**MultiSet Unity SDK**](/multiset/quick-access/multiset-unity-sdk.md)**:** Download and import the latest MultiSet Unity SDK into your project.
3. **Use the** [**Object Tracking Scene**](/multiset/unity-sdk/sample-scenes/modelset-tracking.md)**:** The SDK includes example scenes. Open the "Object Tracking" scene to get a ready-made template and see how the components work together.
4. **Implement the Tracking Manager:** The core of the system is the [Object Tracking Manager](/multiset/unity-sdk/api-reference/modelsettrackingmanager.md). This script is the primary component that handles the connection to the MultiSet service and manages the anchoring of your AR content onto the physical object. Configure it to use your newly created Object Code.

***

### Impact on AR Content and Coordinate Systems

A key benefit of this migration path is the preservation of your existing work.

Because you are using the **same object scan file** that you used for Vuforia, the coordinate system, scale, and pivot point of the model are preserved. This means:

* **No Re-authoring Needed:** All your existing AR content, animations, and interactive elements will work without modification.
* **Consistent Poses:** The poses and transforms returned by the MultiSet SDK will align perfectly with your original Vuforia setup. Your content will appear in the correct position and orientation relative to the physical object.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://multiset.gitbook.io/multiset/workflow/migration-guide/vuforia-model-targets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.