Migrate Tracking Plans from Spreadsheet

Migrate tracking plans created using the tracking plan spreadsheet to the new format for easier management.
Available Plans
  • free
  • starter
  • growth
  • enterprise

  •   2 minute read  

This guide will help you migrate your tracking plans created using the Tracking Plan Spreadsheet to the new format.

Overview

RudderStack lets you easily migrate your tracking plans created using the Tracking Plan Spreadsheet to the new format where you can edit events, properties, and tracking plan rules in the RudderStack dashboard.

Migrate tracking plans

warning

Note that:

  • You must have Admin privileges to migrate the tracking plans.
  • Make sure to see the Migration considerations before you migrate your tracking plans.

You will see the Migration now available banner below the tracking plans created using the spreadsheet:

Tracking Plan migration banner

Go to the tracking plan and click Migrate to start the migration process.

Tracking Plan migration process

Once the tracking plan is migrated successfully, you can view all the events and properties in the dashboard, and make changes as required.

Migration considerations

Once you migrate, note that:

  • RudderStack deletes the old tracking plan.
    • You cannot use the spreadsheet to view or manage the newly created tracking plan.
    • You can manage your tracking plans via the dashboard or the Data Catalog API.
  • You will not see the historical violations or event counts once you migrate your tracking plan to the new format in the RudderStack dashboard.
  • RudderStack supports up to three levels of nesting in the event properties of object or array data type. The tracking plan cannot be migrated if one or more of your event mappings have more than three levels of nesting and you will see the following error:
Tracking Plan migration error
  • RudderStack does not permit certain keywords in the event’s JSON schema. You will get an “Unsupported rules found for event” error if you try to migrate tracking plans having these keywords.

FAQ

Which keywords are not supported while migrating the tracking plan to the new format in the dashboard?

While migrating your tracking plans to the new format, you will encounter an error if your tracking plan rules contain any of the following advanced keywords as event property names:

  • oneOf / allOf
  • if / then / else
  • $def / $ref
  • const
  • default

See the JSON schema guide for the list of all supported keywords.


Questions? Contact us by email or on Slack