How to export all your data from your antique-mall POS — Vintique's full-export workflow

One of the quietest indicators of a well-built SaaS platform is how easy it is to get all of your data out of it. Most antique- mall operators have lived through at least one platform that made export a multi-week ordeal: a phone call to support, a custom CSV request, a wait, a partial export missing the gift card balances or the audit trail, another phone call. Vintique is the opposite. From Settings → Danger Zone you request a full export and it lands in your inbox in minutes — every table, every row, every photo path, every audit entry.

What’s in the export

The full-tenant ZIP archive contains:

• Vendors / booth owners — every booth-owner record including contact info, consignment rate, login association, active/inactive flag, and date trail.

• Items / inventory — every item ever in the system, including drafts, active, sold, and archived. Booth attribution, tag/SKU, price history, tax-exempt flags, and image URLs.

• Transactions — every sale, refund, and adjustment with line-item detail: per-line booth, item, quantity, price, payment split (cash / credit / gift card / split), tax, and cashier ID.

• Gift cards — every card, current balance, original load amount, and the full balance-change audit trail (every sale, redemption, refund, adjustment, with timestamps).

• Holds and collections — every active hold, every customer collection, every consigned-but-not-yet-tagged item.

• Sale events — every storewide and per-booth sale event with start/end timestamps, percent, and exclusions.

• Reports data — daily/monthly/annual rollups so your historical reports stay reproducible after export.

• Settings — tax rate, surcharge rate, branding, number assignments, email sender configuration.

• Users and roles — every cashier, admin, and vendor login (without password hashes; you can re-create logins on a new system).

• Audit log — every administrative action, sign-in, and sensitive change, with actor and timestamp. This is the trail a bookkeeper or auditor will want.

• A README — a plain-text manifest describing every file in the archive, the schema for each CSV, and the ID relationships between files (e.g. how transaction line items link back to items and to booths).

The two scenarios people use it for

1. The operator wants a backup

Most malls take a full export every quarter as a private backup regardless of whether they’re considering a switch. It’s a free peace-of-mind action: download, drop on an external drive, file the date. If anything ever goes wrong, you have a known-good snapshot.

2. The operator wants to leave

If you decide Vintique isn’t the right fit, request the export, cancel the subscription from your Settings page (which opens the Stripe billing portal), and you’re done — no exit fee, no support ticket, no waiting for a manual extraction. The data lives in the ZIP, your card stops being charged at the end of the current billing period, and the workspace enters a 30-day grace window before anything is permanently deleted.

The 30-day grace window

When you schedule a workspace for deletion, nothing is removed immediately. The mall enters a 30-day grace period during which you can:

• Download the full export at any time (the export endpoint is still live).

• Restore the workspace if you change your mind — sign back in, hit restore, and the mall is back exactly as it was.

After 30 days, a daily background job permanently removes the tenant: database rows, object-storage photos, sessions, and audit records. The deletion is recorded one final time in our internal platform audit log so we have a record that the deletion happened, but the mall’s content itself is gone.

How to request an export today

1. Sign in as a workspace admin.

2. Go to Settings → Danger Zone → Export workspace.

3. Confirm the request. Most exports finish in a few minutes; very large malls may take up to an hour.

4. You’ll get an email with a download link to a signed URL valid for 24 hours. Download the ZIP, verify the file count against the README, and file it where you keep your other operational backups.

For more on the broader tenant lifecycle (suspend, soft-delete, restore, hard-delete), see the platform documentation. For the migration playbook used by operators leaving a legacy POS in either direction, see

. If your old system is specifically Quail Mall Manager (Antique Mall Accounting), there’s a Quail-specific version of the same playbook with the exact reports to pull and the column names our auto-mapper already recognizes:

.