Data settings
Custom fields let you store things CIQRA did not anticipate. The two export destinations let you leave with your data. Custom data, the other half of extending CIQRA’s model, now lives under Content → Custom data in the sidebar.
What is in this group
Section titled “What is in this group”| Destination | What it governs |
|---|---|
| Custom fields | Extra fields attached to things CIQRA already knows about, such as a product or a customer. |
| Data export | The older, collection-by-collection export. It can produce a data-only archive; see the warning below. |
| Export your data | Taking a complete copy of your store out of CIQRA — every table, portable files, your media, and an API for the provider you move to. |
Custom data and custom fields answer different questions
Section titled “Custom data and custom fields answer different questions”They look similar and are not. A custom field hangs off something that already exists: a product gains a “care instructions” field. Custom data is a thing in its own right — a “store event” or a “size guide” that is not an attribute of anything else and needs its own list.
The rule of thumb: if deleting the product should delete it, it is a field. If it should outlive the product, it is custom data.
Export exists so that leaving is possible
Section titled “Export exists so that leaving is possible”Export your data is listed under Settings rather than buried, deliberately. A platform that makes it hard to leave is a platform you cannot safely evaluate. Under the EU Data Act it is free, and it is yours for 60 days after your store closes (30 days of transition and 30 days of retrieval), in a read-only admin that keeps only Export and Billing.
What the export contains. Only the store owner can ask for it, confirming it is them each time. It is built in parts you download one by one:
- a database archive with every table your store holds, whose own
manifest.jsonlists exactly what it contains; - a portable copy of the same data: JSON with its schemas, and CSV files, readable without CIQRA;
- Shopify-format CSV for products and customers;
- your media, theme, legacy-site and form-upload files as ZIP parts (the files can be large, so they are split);
- your invoices;
- optionally, activity and application logs. They hold personal data, so they are off by default, IP addresses are masked unless you turn that off, and you become the data controller of that copy.
When an export is ready, Open verification report shows whether every part and every file matched when it was re-hashed on the server. The files can be downloaded for a limited time, and each download asks you to confirm it is you.
Passwords, API keys and the credentials of your integrations are never included.
Switching to another provider. The same screen has a Switching to another provider section: tell CIQRA you are switching (optionally naming the new provider), and create API access tokens. A token is shown once, only read access to your exports, and can be revoked at any time. The new provider calls the switching API with it.
🔴 Backup & export is a different screen. The backups list under Settings > Data export (the older, collection-by-collection export) can produce a data-only archive: it holds the database rows but not your media, theme and legacy files, so a “Verified” badge means the zip matches its own manifest, not that it is the whole store. Those rows carry a “Data only: files not included” badge, and the page links to Export all data including files.
What this page does not say
Section titled “What this page does not say”- It does not describe custom data itself. That moved to Content; see Metaobjects and their entries.
- It does not cover backups. Data export is a copy you ask for; the platform’s own backup and restore posture is described under Transparency, with dates and measurements.