Vivantio — Migration Reference

Vivantio — Migration Support Overview

Role in migrations

• Staff (HD): supported as both (source and target).
• Company (HD): supported as both (source and target).
• Contact (HD): supported as both (source and target).
• Ticket (HD): supported as both (source and target).
• Category (KB): supported as both (source and target).
• Folder (KB): supported as both (source and target).
• Article (KB): supported as both (source and target).

Field-level support migrating FROM Vivantio (Ticket)

Field-level support migrating TO Vivantio (Ticket)

Field-level support migrating FROM Vivantio (Company)

Field-level support migrating TO Vivantio (Company)

Field-level support migrating FROM Vivantio (Contact)

Field-level support migrating TO Vivantio (Contact)

Field-level support migrating FROM Vivantio (Article)

Field-level support migrating TO Vivantio (Article)

Migration options available for Vivantio

• Migrate the newest records first - applies to: source (Ticket)
• Select records for Demo - applies to: source (Ticket)
• Inline images in tickets - applies to: source (Ticket)
• Skip ticket attachments - applies to: source (Ticket)

Vivantio — Setup & How-To Guide

For more information: https://help-desk-migration.com/help/vivantio-migration-guides/

How to Connect Vivantio to Migration Wizard?

Prior to connecting Vivantio to the Migration Wizard, make sure you have an active account with administrative privileges. This will grant you the ability to configure and access the required settings.

Here’s a step-by-step guide to finding the URL, username, and password:

1. Log in to your Vivantio account.
2. Hover over to Admin in the left navigation.
3. Scroll down and choose Downloads under Integrations & API.
4. Copy the URL, username, and password on the new page.
5. Return to Migration Wizard and provide the access credential.
6. Once you’ve done that, continue setting up a Free Demo.

OpenDate and CloseDate migration

By default, ticket creation and closing dates don't migrate. To make them migrate, Vivantio needs to make changes on the client's account. The client should contact Vivantio and request that they enable importing data into the OpenDate and CloseDate fields. Once Vivantio makes this change, the migration tool will automatically migrate this data without any changes needed on our side.

Problems and Changes

In Vivantio, Problems and Changes are governed by ticket types. A default migration for Problems and Changes isn't possible, because clients can create custom types with any name they like, and can also rename the types that exist by default. Because of this, at the source and target settings step, we display the type to migrate from. These types aren't split by any fixed criteria or category indicating whether something is specifically a Change or a Problem — it's just a type, and the client decides how to treat it.

Migrating from different ticket types on Vivantio's source side can be done as a custom migration, but migration to Vivantio only goes into a single ticket type. This means that if different ticket types need to be migrated to Vivantio, this must be done in separate migrations — since different ticket types have different custom fields, statuses, priorities, impact levels, and categories.