In this article we will describe the process of migrating existing user data to a better analytics platform (in our case, it is devtodev). How is it done? What do you need to pay attention to? How long does it take? Find all the answers in the article below.
If for some reason (lack of functionality, etc.) you want to migrate to devtodev from another analytics platform, move all your data from your in-house analytics system, or use the data stored on your servers, feel free to use our Import Data Wizard.
You can import any data about users or events that are allowed by the devtodev data API. The most frequent task is to import an existing user database (with information about registration dates, player character levels, and other characteristics), data on payments, and user sessions. Also you are free to send us other events but it is not reasonable to cover a period longer than 90 days from the import start date.
Read more: How to Create an Ideal Dashboard for Analyzing Mobile Games and Apps
The main condition for the successful import of historical data is to match the IDs that are currently used for user/device identification and sent to you by devtodev SDK built into your project, with the IDs in your possession — the IDs to which you can link the imported historical data to.
The best option of importing historical data is when you set custom user ID tracking in the devtodev platform. A custom user ID used in devtodev is an ID assigned by the developer. This is usually the number of the record about the user in your database or a third-party ID by which you authorize and identify the user.
To start the process of exporting historical data, go to the settings of the project into which you want to load historical data and select Import Historical Data.
Read more: How to Integrate an Analytics System into your Game
How to Actually Migrate Your Data?
1. Preparation stage: it consists of creating a temporary project in devtodev and preparing your historical data.
2. Data loading stage: just make a couple of clicks and the loading process starts.
3. Processing uploaded data: at this stage, devtodev transfers the uploaded data to its database and calculates metrics for this period of time. At the end of the data processing, the interface for loading historical data will automatically proceed to the next step — data verification. It may take up to several days depending on the size of your database.
4. Reviewing the loaded data: this is an extremely important step in the data loading process because it is here that you understand whether you did everything right and are satisfied with the result, or something went wrong, which means that you have to implement the necessary changes and try importing again.
That’s it! Try it, it’s really easy!
You can find more practical information about time that the process takes, limitations, right user IDs, and even some tips in the devtodev documentation. We wish you a smooth migration!
