Importing your data
Moving to Paysio from another processor? You can bring your history with you, so your customers and reporting carry over instead of starting from scratch. This is done on the Settings > Data Import page.
What you can import
Data Import pulls your customers and transactions from NMI or Stripe. You need that processor connected first (see Payment processors), since Paysio uses its connection to read your history.
Products and mailing-list subscribers are imported separately, from files, on their own pages. See Importing products via the Products page, and the customer file import on the Customers page.
Full vs incremental imports
There are two ways to run an import:
- Full Import: a complete backfill that pulls all of your history from the source. Use this the first time you move over.
- Sync New: an incremental import that pulls only records created since your last import. Use this to top up after a full import, so you catch anything new without re-importing everything.
Each button lets you pick the source (NMI or Stripe) before it runs.
Running an import
Choose Full Import or Sync New, pick the source, and Paysio starts the job. It imports your customers and transactions together, and only one import runs at a time.
While it runs, you see live progress: the job's status updates in real time (pending, running, completed, failed, or cancelled), and you can expand a job to watch its logs stream as it works, color-coded so warnings and errors stand out. Because it streams live, you can leave the page and come back to check on a long import.
Reading the results
Each import job reports four counts so you know exactly what happened:
- Fetched: how many records were read from the source.
- Imported: how many were successfully brought into Paysio.
- Skipped: records that were not imported, usually because they already exist (so re-running is safe).
- Errors: records that failed, with details in the logs.
A job also shows how long it took and its final status. If something went wrong, expand the logs to see why.