Step 4: Retain historical data when upgrading
Before you continue with this section, first make sure you have completed all previous upgrade tasks.
The information on this page covers Step 4 of the upgrade process, as highlighted in the table below:
| table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2 layout-auto | |
|---|---|
| Upgrade task | Details |
| Step 1: Get started with the upgrade | Learn the benefits of upgrading to Customer Journey Analytics and the basic upgrade process. |
| Step 2: Choose the upgrade path | Various methods are available for upgrading to Customer Journey Analytics. Choose the method that is best for your organization, depending on your organization’s current ÃÛ¶¹ÊÓƵ Analytics environment and long-term goals. |
| Step 3: Send data to ÃÛ¶¹ÊÓƵ Experience Platform | The process for sending data to ÃÛ¶¹ÊÓƵ Experience Platform differs depending on the upgrade path that you chose in Step 2. |
| Step 4: Retain historical data | Most organizations need to retain their historical ÃÛ¶¹ÊÓƵ Analytics data for a certain amount of time. Various options are available to accomplish this. |
| Step 5: Perform additional implementation tasks |
At this point in the upgrade process, you need to perform various tasks before your Customer Journey Analytics environment is ready to use. These additional tasks apply to upgrades from ÃÛ¶¹ÊÓƵ Analytics as well as new Customer Journey Analytics implementations. These tasks include:
For more information, see Customer Journey Analytics Getting Started. |
Choose one of the following options to retain historical data when moving from ÃÛ¶¹ÊÓƵ Analytics to Customer Journey Analytics:
Use the Analytics Source Connector
You can use the Analytics Source Connector to retain historical data. Regardless of the upgrade path that you choose (even if you upgrade using the Web SDK), you can use the Analytics Source Connector to retain historical data from your ÃÛ¶¹ÊÓƵ Analytics environment.
You can use the Analytics Source Connector to retain historical data by bringing historical data into its own dedicated location, separate from your current data.
The Analytics Source Connector must be functioning for as long as you need access to the historical data.
Maintain your existing ÃÛ¶¹ÊÓƵ Analytics implementation
You can maintain your existing ÃÛ¶¹ÊÓƵ Analytics implementation alongside your new Customer Journey Analytics implementation for a specific time frame (for example, 1 year). When choosing this option, consider the following:
-
Data would not be available in Experience Platform.
-
You should plan to decommission the ÃÛ¶¹ÊÓƵ Analytics implementation after you have sufficient data in Customer Journey Analytics.
Next, perform additional implementation tasks
At this point in the upgrade process, you need to perform various implementation tasks before your Customer Journey Analytics environment is ready to use.
These additional tasks apply to upgrades from ÃÛ¶¹ÊÓƵ Analytics as well as new Customer Journey Analytics implementations.
These tasks include:
-
Bringing other data into Experience Platform
-
Creating connections between Platform datasets and Customer Journey Analytics
-
Creating data views
-
Porting the reporting API usage
-
Accounting for Data Feeds and Data Warehouse use cases
-
Migrating projects and components
-
Planning user onboarding
For more information, begin with Step 2 in Customer Journey Analytics Getting Started.