Demo Migration Checklist

Last updated: April 20, 2026

A step during the migration process will be a "demo migration", where the Pylon team will assist in kicking off a migration of 20 tickets (randomly selected, or hand-picked). The purpose of this is to allow you to "preview" what these migrated issues will look like in Pylon.

Reviewing your Imported Demo Tickets

In the Pylon issues board, adjust the date filter to look at tickets created in the past 2 years and filter for Issue Tags == imported .

image.png

Here are some things to confirm during the demo migration process:

  • [Issues] Custom Issue Fields

    • Ensure that all the mapped fields are pulling over as expected.

  • [Issues] SLAs

    • Ensure metrics such as First Response time and Resolution time are correctly pulled in for reporting / analytics purposes.

  • [Issues] Filtering

    • By default, all tickets will get pulled into Pylon. We often recommend only pulling in 6 months-2 years worth of data, so make sure you confirm with our team over what timeframe you'd like to migrate tickets from.

    • Additionally, if there are specific issues you'd like to omit (eg. ignore tickets that have a spam tag), please let us know!

  • [Knowledge Base] Article Formatting & Content

    • Confirm that the article content is correct and is formatted correctly.

  • [Knowledge Base] Collection Hierarchy

    • The migration should maintain any folder nesting from your source system. Confirm that these are maintained.