Fast Track

Data Migration is a critical step to ensure all historical data (prior to the activation of the FT Real Time Feed) is successfully migrated into the FT Database. This step ensures proper data alignment between the platform and FT.

Recommended Tables for Data Migration

- Login Activity
- User Balance Activity
- Payment Events
- Casino Activity
- Sports Activity
- Bonus Activity

Only the Payment Events table consists of raw event data.

All other tables are activity tables, containing aggregated data.

Additional tables can be selected from the Data Migration Portal available in your FT instance:

Navigation: Integration → Data Migration

Use the Data Migration Portal to select the required tables and fields.

Save the selection to auto-generate the CSV templates.

Download the templates and fill them with historical data.

1. Use the Data Migration Portal to select the required tables and fields.
2. Save the selection to auto-generate the CSV templates.
3. Download the templates and fill them with historical data.

Upload the filled CSV files to the TEMP tables via the portal.

QA verification is performed on the uploaded data.

Approval must be granted before proceeding.

- Upload the filled CSV files to the TEMP tables via the portal.
- QA verification is performed on the uploaded data.
- Approval must be granted before proceeding.

A timestamp will be provided by FT.

Platform must regenerate CSV files, updating data up to the provided timestamp to ensure no data discrepancy occurs.

FT will stop “consumer” services (RTF events will still be received but queued).

FT begins the actual data migration.

- A timestamp will be provided by FT.
- Platform must regenerate CSV files, updating data up to the provided timestamp to ensure no data discrepancy occurs.
- FT will stop “consumer” services (RTF events will still be received but queued).
- Final CSVs are uploaded.
- FT begins the actual data migration.

Upon successful migration, FT services will resume.

Accumulated messages in the queue will be consumed and normal RTF processing will continue.

- Upon successful migration, FT services will resume.
- Accumulated messages in the queue will be consumed and normal RTF processing will continue.

The duration of the migration process primarily depends on how quickly the platform can prepare and deliver the CSV files.

Once files are received, data migration typically completes within two working days, depending on data volume.

- The duration of the migration process primarily depends on how quickly the platform can prepare and deliver the CSV files.
- Once files are received, data migration typically completes within two working days, depending on data volume.

Handling Large Volumes of Payment Data

If your Payment Events volume exceeds 1 million records, we recommend migrating Payment Activity instead.

Migrating Payment Activity instead of Payment Events will result in loss of historical data functionality in:

- Data Studio
- Player Features

Data Migration

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

Data Migration

Data Migration Overview

Recommended Tables for Data Migration

CSV File Preparation

Migration Steps

1. Dry Run

2. Full Run

3. Post-Migration

Important Notes

Handling Large Volumes of Payment Data