Import and export
Bringing a push list over from another provider, exporting yours, and why an imported endpoint may not work.
Export
Subscribers → Export CSV, or Import subscribers → Export CSV.
You get a dated file (qpushly-subscribers-YYYY-MM-DD.csv) with your full list.
Worth doing before you uninstall, before a migration, and periodically as a backup — your list is one of the few things in the app you cannot rebuild.
Import
Qpushly → Import subscribers. Drop in a .csv exported from your previous push
provider, or a file you built yourself.
After the import you get four counts and, if any rows failed, the reasons:
| Count | Meaning |
|---|---|
| Imported | New subscribers created |
| Updated | Existing subscribers matched and refreshed |
| Failed | Rows that could not be used |
| Total | Rows read |
Skipped rows are listed with a reason, so a failed import is diagnosable rather than mysterious.
What an import can and cannot do
Two more things to know:
- You cannot import an email list as push subscribers. There is no way to manufacture a push endpoint from an email address. Those shoppers have to opt in from your storefront.
- Importing does not trigger welcome notifications. Imported subscribers are not new opt-ins, so the welcome automation does not fire for them. That is deliberate — a welcome message to someone who subscribed a year ago on another platform is confusing.
Migrating from another provider
- Export from the old provider before you cancel — some remove your data immediately on cancellation.
- Install Qpushly and enable the theme embed so new subscribers start arriving.
- Import the old list. Read the skipped-row reasons.
- Run both for a short overlap if the old provider allows it, so you can compare delivery.
- Send one campaign to the imported list and compare its impressions against the number of rows imported. That difference is your real attrition.
- Turn off the old provider’s storefront script. Two push tools on one storefront means two service workers competing, which produces exactly the sort of intermittent bug that takes days to find.
CSV format
Export a file from Qpushly first and use it as the template — matching its columns is the reliable way to get an import accepted. The push endpoint and its two keys are the fields that actually matter; everything else is metadata.