What does “Demo migration is suspended” Mean? [+Video]

As you breeze through the stages of your Demo migration, meticulously filling out each field with the correct credentials and eagerly setting up your Demo to revel in the results, you're suddenly halted. The Migration Wizard, however, delivers a disappointing blow, informing you that your Demo migration has been suspended.

Let us shed light on why opting for this particular choice is your sole option and why retracing your steps to the previous stage is not feasible. In this article, we will delve into the underlying reasons that can potentially hinder a successful data migration process.

Why Demo Migration Is Suspended: Unraveling the Mystery

In the realm of data migration, a multitude of errors can potentially spell failure. These errors are intricately tied to the idiosyncrasies of both the source and target help desks or services involved in the migration process. Each platform has its unique structure and data organization approach, setting it apart from others.

When embarking on a Demo migration, it's crucial to prepare diligently, lest you encounter pitfalls.

• For instance, when migrating your Knowledge Base to Zendesk, it's imperative to ensure that your Zendesk Guide feature is activated. Without it, you won't be able to select the knowledge base during the mapping stage.
• Duplication issues are another roadblock to watch out for. Some platforms prohibit the creation of records or fields with identical parameters. For instance, Salesforce Service Cloud disallows the creation of categories with the same name, while Gorgias prohibits the creation of two User Contacts with the same phone numbers.
• Moreover, platforms that utilize OAuth identification necessitate an access token for API access during data migration. If your access token has expired or been refreshed, our tool won't be able to establish the necessary API connection, thwarting the migration process.
• Furthermore, invalid or suspended contacts cannot be processed or created on the target platform using our migration service.

As you can see, the errors that can cause the migration to fail are strictly dependent on the platforms you choose.

Empowering you to take control: navigating a suspended migration

Finding yourself in a suspended migration situation can be overwhelming, but fear not! There are two proactive steps you can take to get back on track.

The first step involves checking why your Demo Migration got suspended.

If it's due to skipped records or any other issue, it's best to wait for our stellar support team to reach out and assist you in resolving the hiccup.

So you can resume your test migration with confidence. Our support team is armed with all the information needed to identify the problem and guide you on the next steps.

The second scenario is when you notice failed records in the results of your Demo migration. Not to worry!

You can easily identify the reasons for the suspension by reviewing the record IDs, and then take action to fix the issues. Once you've addressed the errors, simply check the box labeled 'I've fixed errors' and hit the 'Restart Demo' button to get your migration back on track.

If you have any questions or need further assistance, our live chat support reps are always ready to lend a hand. We're here to empower you every step of the way!