Import from Tebex
Migrate your order history and customer data from Tebex to FluxStore using a CSV import.
Import Workflow
Export your data from Tebex
Export your transaction history from Tebex as a CSV file. Make sure the export includes transaction IDs, customer usernames, package names, amounts, and dates.
Upload the CSV
In FluxStore, go to Dashboard > Import/Export > Import. Click Upload CSV and select your Tebex export file.
The maximum upload size is 50 MB. If your export exceeds this limit, split it into multiple files and import them separately.
Auto detection
FluxStore automatically detects the source as tebex based on the CSV column structure and displays the detected currency. Verify both before proceeding.
Review extracted data
A preview table shows the first rows of extracted data. Review the package names, amounts, usernames, and dates to confirm the CSV was parsed correctly.
Map packages
FluxStore displays a list of unique package names from the CSV. For each one, select the corresponding FluxStore package from a dropdown, or choose Skip to exclude those transactions.
You do not need to map every package. Skipped packages are excluded from the import but do not cause errors.
Configure import options
| Option | Default | Description |
|---|---|---|
| Skip Duplicate Transactions | On | Skip transactions with IDs that already exist, preventing double imports. |
| Create Missing Customers | On | Automatically create customer profiles for usernames not in your store. |
| Mark as Imported | On | Tag imported orders with an “imported” flag to distinguish them from native orders. |
Execute the import
Click Start Import to begin. A progress indicator shows records processed, created, and skipped. You can click Cancel Import at any time. Records already imported are kept, and running it again with skipDuplicateTransactions enabled will skip them.
What Gets Imported
| Data | Imported | Notes |
|---|---|---|
| Transaction ID | Yes | Used for duplicate detection |
| Customer username | Yes | Matched to existing customers or created if Create Missing Customers is enabled |
| Package name | Yes | Mapped to a FluxStore package during the mapping step |
| Transaction amount | Yes | Stored in the original currency |
| Transaction date | Yes | Preserves the original purchase timestamp |
| Payment gateway | No | All imported orders are tagged as “imported” |
| Delivery commands | No | Commands are not run again for imported orders |
Imported orders are display only records. They do not trigger delivery commands, webhooks, or email notifications. They exist purely for historical reporting.
Tips for a Smooth Migration
- Create your packages first. Set up all your FluxStore packages before importing so you have targets for the package mapping step.
- Start with a small test. Import a small date range first to verify the mapping is correct before importing your full history.
- Keep duplicate protection on. Leave Skip Duplicate Transactions enabled so you can safely run the import again if needed.
- Check currency. Verify the detected currency matches your Tebex store currency. Mismatched currencies result in incorrect revenue figures.
- Review after import. Spot check a few imported orders in Dashboard > Orders to verify amounts, dates, and customer assignments.