Import from Enjin
Migrate your historical order data from a legacy Enjin Minecraft store into FluxStore using a CSV import.
Enjin is a discontinued platform and its exports are a legacy, best-effort format. The import may not handle every export cleanly, so review the preview carefully before running it. Enjin orders also have no Minecraft UUID, so they are matched by username only and are imported purely as display-only historical records.
Import Workflow
Export your data from Enjin
Export your transaction history from Enjin as a CSV file. The expected columns include the item name, gateway, transaction ID, date, time, Minecraft username, currency, amount, and status.
Upload the CSV
In FluxStore, go to Dashboard > Import/Export > Import. Click Upload CSV and select your Enjin export file.
The maximum upload size is 10 MB. If your export exceeds this limit, split it into multiple files and import them separately.
Auto detection
FluxStore detects the source as enjin from the CSV column structure and displays the detected currency. A warning is shown to remind you that this is a legacy format. Verify the source and currency before proceeding.
Review extracted data
A preview table shows the first rows of extracted data. Because Enjin exports vary, spend extra time here: confirm the item names, amounts, usernames, and dates parsed correctly.
Map packages
FluxStore lists the unique item names from the CSV. For each, select the corresponding FluxStore package, or choose Skip to exclude those transactions.
You do not need to map every item. Skipped items 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 |
| Minecraft username | Yes | Matched to existing customers or created if Create Missing Customers is enabled |
| Minecraft UUID | No | Enjin exports do not include a UUID, so orders are matched by username only |
| Item name | Yes | Mapped to a FluxStore package during the mapping step |
| Amount | Yes | Stored in the original currency |
| Transaction date and time | Yes | The separate date and time columns are combined into the original timestamp |
| Payment gateway | Name only | The gateway name is kept for display. Enjin is no longer operational and provides no usable transaction reference, so imported orders cannot look up live payment details. |
| 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, and they have no live payment data to query from a gateway. 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 item mapping step.
- Start with a small test. Import a small slice of your history first to confirm the legacy export parses correctly before importing everything.
- Keep duplicate protection on. Leave Skip Duplicate Transactions enabled so you can safely re-run the import.
- Check currency and dates. Enjin’s date format and currency are detected automatically, but verify them in the preview.
- Review after import. Spot check a few imported orders in Dashboard > Orders to verify amounts, dates, and customer assignments.