Import metadata support
You can now include custom metadata in your affiliate, customer, and sale imports.
Add any key-value data to your CSV and it gets stored against each record. Real datasets always carry more context than a fixed schema anticipates — the campaign a sale came from, the region an affiliate covers, the internal ID your other systems use for a customer. Before this, that context got dropped at the door during migration. Now it comes with.
Common uses:
- Tag affiliates with signup source or region, and keep segmenting by it after migration.
- Store internal IDs for customers, so records stay joinable against your CRM or billing system.
- Add campaign or channel details to sales for richer attribution analysis later.
Map the metadata column during the import wizard's field-mapping step, and you're set — the wizard treats it like any other destination field.
If you're switching platforms, this is the difference between importing your records and importing your records with their history attached. Nothing about your old system's context needs to be left behind.