Migration
Move without breaking a single link
Migration is a product feature, not a services project. Import your entities, point your legacy tracking domains at Metrixed, and links already in the wild keep tracking.
Importers
Supported sources: TUNE, Everflow, Trackier, Affise, CAKE, CSV.
Dry run first
Every import can run as a dry run that shows a diff of what would be created, before anything is written.
Resumable
Imports run in chunks and resume where they stopped, with an id map from old ids to new ones.
CSV with mapping
For platforms without an importer, upload CSV and map columns to fields.
Platform importers are built from public API documentation and fixtures. Expect to confirm field mappings for your account during a dry run.
Legacy link compatibility
Register your old tracking hostnames as legacy domains. At the edge, Metrixed maps old offer and partner ids through the id map and translates old parameter names (for example TUNE aff_unique parameters, Affise sub-ids beyond five and CAKE udid) into its own event parameters, so destination macros and reports still see them.
Conversions that arrive at your old platform after you cut over can be forwarded, so late postbacks are not lost.
Typical sequence
- Connect the source account and run a dry run import.
- Review the diff, then import entities and history you want to keep.
- Register legacy tracking domains and point DNS at Metrixed.
- Turn on forwarding for late conversions, watch the migration checklist, and retire the old account.
Known limits today: forwarding covers newly created conversions only, and legacy sub-id translation runs after rule sets, so rules that match on translated names see the original names.
Comparison facts elsewhere on this site are as of 2026-10-17.
Plan your migration
Tell us which platform you run today and roughly how many offers and partners you have.