TB Oracle
Migration

How to switch Total Battle trackers without losing clan history

A migration checklist for moving Total Battle chest, member, RSS, and event history from another tracker or spreadsheet.

Changing trackers should improve the clan record, not reset it. Preserve the raw source, agree on identity and date rules, and validate a small sample before importing the full history.

Freeze a source export

Export the original data before changing fields or cleaning names. Keep one untouched file and work from a copy. Record the export timezone and the date of the last complete collection.

Map identities carefully

Player names change and can be reused. Prefer stable game entity IDs when the source has them. Build a review list for ambiguous names instead of merging them automatically.

Define the cutover

Choose the final timestamp for the old tracker and the first timestamp for the new one. A short overlap is useful for validation, but duplicate rows in that overlap need a clear rule.

Validate totals and samples

Compare total rows, date ranges, several individual members, and source breakdowns. Keep a written note for fields the old system did not capture so nobody treats missing history as zero activity.

Request a historical import

See your own clan record.

Start a 30-day trial with no credit card, then request a historical import from Settings if you are switching tools.

Start free

Keep reading