If you have a new website, or you’re migrating your existing website from one platform to another, we recommend taking the following steps to ensure that your Heap data governance will not be impacted by the change.
Review your existing event structure and update event definitions in preparation for the site migration. As an example, you could update the name of all of your existing events to prefix it with something like Old App – Click – Sign Up. Once you are set up to create events for the site on the new platform, you can use combo events to combine the old and new event definitions for continuity of data.
Alternatively, if you’re comfortable editing CSS, you can add a comma into your existing event definition and add the CSS selectors for your new platform to keep both definitions in one place. For more info, see Capturing Multiple Versions of an Event.
We always recommend using naming conventions for your definitions to maintain an organized and trustworthy dataset. For more information, see Event Naming Conventions.
Note that renaming events that are synced to Heap Connect will automatically rename those tables. You may need to coordinate with your Heap Connect admins prior to updating the names of any synced events.
Once your event definitions are updated, you’re ready to install Heap on your new platform! Once you’ve confirmed that data is flowing into Heap, you can use the visual labeling and Live data feed to set up your new events and combo events.
You’ll also need to update your reports to use these new combo events. We recommend adding notes to your reports to denote any important caveats or differences, and using footnotes on usage over time charts to tag specific dates.
After the migration is complete, you’ll also want to check the Event Repair Flow to check for any event definitions that were broken during the migration.