How to Import Transactions and Orders via CSV in Sparkforge
Sparkforge accepts CSV imports for both transactions and orders, so you can backfill historical revenue from prior platforms. Records flow into dashboards immediately, and contacts match by email or phone before duplicates are created.
Sparkforge supports bulk CSV import for both transactions and orders. Use it to bring historical revenue from previous platforms into your Sparkforge sub-account so dashboards, contact timelines, and reporting reflect a complete picture.
Transactions vs orders
A transaction records a payment event. An order records itemized line items and automatically generates a linked transaction. Importing orders impacts both order and transaction reporting; importing transactions impacts revenue only.
How to import transactions
- Go to Payments > Transactions.
- Click Import.
- Download the sample CSV and match your data to the required format.
- Upload your file and review the preview modal for validation errors.
- Confirm the import. Revenue dashboards update immediately.
How to import orders
- Go to Payments > Orders.
- Click Import and upload your formatted CSV.
- Validate in the preview modal.
- Confirm. Each order auto-creates a matching transaction and impacts revenue reports.
CSV field rules
- Field names must match the sample exactly.
- Customer details are required so records match an existing contact (by email or phone) or create a new one.
- You can set the actual transaction date separately from the ingestion date — useful for backdating.
What's not supported
Refunds and voided transactions can't be imported. Only successful, completed transactions and orders are accepted.
Frequently Asked Questions
Will importing duplicate existing contacts?
Can I backdate a transaction?
What if my CSV has errors?
Can I import refunds?
Does importing affect revenue dashboards?
Was this article helpful?
Thanks for the feedback.