Moving Off Wix: How to Preserve Your Form Submission History

Most people who decide to migrate from Wix to a custom website plan the pretty part first. New design, faster pages, a CMS they actually control. Then, three weeks in, someone in sales asks a quiet question: what happens to the four years of enquiries sitting in the contact form?

That question belongs in the brief before development starts. Rebuilding a contact page does not transfer its historical submissions, and an attractive new form is little help if sales cannot find an earlier conversation.

Treat preserving those records as a separate deliverable with its own acceptance checks.

Why form history is the hard part of leaving Wix

A Wix site is really two things stitched together: the front end your visitors see, and the data your business quietly accumulated behind it. Moving visible content and preserving private enquiry records require different checks.

Every "Request a quote," every "Book a call," every newsletter signup wrote a row into a table you don't own the storage for. Do not assume cancelling a paid plan, deleting a site and closing an account have identical effects. Confirm the current consequences for your account before changing any of them.

Ask who is responsible for exporting, importing and checking the records. If the quote only mentions rebuilding pages, this work may not be included.

What you can actually get out

Here's the good news. For standard Wix Forms, submissions collect in a submissions table you can view, filter, and export to CSV per form (Wix Support: Viewing and managing a submissions table).

Wix also provides a combined dashboard view. Regardless of the view you use, reconcile each form separately so differently named fields and missing date ranges are easy to spot.

Two things trip people up here.

First, filters. If your view is filtered when you export, you may only pull the filtered rows. Clear every filter first, confirm the row count matches the total, then export.

Second, form type. Wix has more than one way to build a form. A custom form wired into a CMS collection stores its data in that collection instead, which is a separate export path (Wix Support: Creating a custom form). Before you assume one big CSV covers everything, list every form on the site and check where each one actually writes.

The gap nobody warns you about: attachments and payments

CSV gives you the text. It does not always give you everything attached to that text.

For file uploads, inspect a sample export to see whether it contains a file reference, a usable download link or neither. A row containing a filename is not a backup of that file. Preserve authorised attachments separately and confirm they open from the destination without relying on the old account.

Payment and order data is its own trap. Wix documents an export limitation for order/payment details and total amounts. Do not assume a PDF export fills that gap. Don't assume the money side rode along with the enquiry text. Reconcile it against your payment records separately, or you'll discover the gap during an audit, which is the worst time.

Illustrative concept images are used in this guide.

A worked example: the fictional interiors studio

Picture a made-up Dubai interiors studio, "Cedar & Co." Not a real client — just a clean case to think through.

They have three forms: a general contact form, a "book a consultation" form, and a project brief form with file uploads. Over four years that's roughly 2,100 rows combined.

Their instinct is to export one CSV and cancel Wix that afternoon. That would have quietly lost the project briefs, because those files were references, not embedded data, and the brief form turned out to be a CMS-collection form with different columns from the other two.

The workable sequence looks like this. They export each of the three tables separately with filters cleared. They bulk-download the attached brief files into a dated folder. They keep the Wix plan alive for one extra billing cycle as insurance. Only after the imported data is confirmed searchable in the new system do they cancel.

Their overlap period is a planning choice, not a Wix requirement. Another business might need a different period based on its migration risk and billing arrangements.

Making old records queryable in the new site

Getting a CSV is step one. A folder of CSV files is an archive, not a system. A protected spreadsheet can be enough for occasional lookups, provided the people who need it know how to find and use it.

If staff need the history every day, putting it beside current enquiries may justify the extra import work.

Two realistic routes:

Import into your new database. Map the Wix columns to your new schema — name, email, message, date, source form — and load them as historical rows flagged with their origin. Ask for this explicitly in your custom website development brief if historical and current enquiries need one search interface.

Keep a read-only archive. If the old data doesn't need to mix with live records, load the CSVs into a simple searchable table or a lightweight database and leave it read-only. Cheaper, faster, fine for reference-only history.

Whichever route you choose, nominate one authoritative archive. Several unexplained files called `contactformfinal_v2.csv` make it hard to know which version staff should trust.

Column mapping is where hours disappear

Budget real time for the unglamorous mapping work. Wix column names rarely match what you want long-term. Timestamps come in one format; you may want another. One form calls it "Message," another calls it "Project details."

Decide your target columns once. Then map each export into them. Do the smallest form first as a dry run — then test the full dataset for exceptions. A small successful sample does not prove that every record will import correctly.

Keep the raw original exports untouched in a separate folder. When a mapping decision turns out wrong, you re-run from the raw file instead of re-exporting from a Wix account you may have already closed.

Check the records the totals can hide

Matching the source and destination row counts is necessary, but it is not sufficient. Two imports can have identical counts while one has lost message text, moved a date into the wrong column or duplicated an enquiry and dropped another. Keep a reconciliation sheet showing the source form, export date, destination count and any exceptions still awaiting a decision.

Choose a deliberate sample: the earliest and latest enquiry, a long message, an Arabic name, a phone number beginning with a plus sign, a blank optional field and a submission with an attachment. Compare each record field by field. Import phone numbers as text so a spreadsheet does not remove leading zeros or alter international formatting.

Wix says exported submission dates use UTC. Preserve that meaning when importing. Store the original timestamp and decide separately how the new interface displays local time. A record near midnight is a useful test because an unnoticed time-zone conversion can move it onto the wrong reporting day.

Keep the archive private and plan the final handover

Historical enquiries may contain personal contact details and private project information. The archive belongs behind appropriate access controls, not in a publicly reachable website folder. Give the migration team only the access it needs, transfer exports securely and agree when temporary working copies will be removed after acceptance. Retain records according to the business's established policy rather than keeping everything indefinitely by default.

Finally, account for enquiries received between the first export and launch. Agree a cutoff time, take a final incremental export or repeat the export safely, and reconcile by a stable source identifier where one is available. Never use email address alone as a unique key: one customer can submit several legitimate enquiries. Test the new form's confirmation, staff notification and storage path before switching traffic.

The pre-cancellation checklist

Run this before the Wix plan lapses, not after:
• List every form on the site and note where each stores data (standard submissions table vs CMS collection).
• Clear all filters, then export each form's table to CSV. Confirm exported row count matches the total.
• Preserve required uploaded files using the export or download options available in your account; check them individually against the records.
• Reconcile any payment or order totals separately — assume they're not in the CSV.
• Screenshot or export any automation and notification settings you'll need to rebuild.
• Import into the new database (or a read-only archive) and confirm you can search a known old enquiry.
• Agree an overlap and rollback period based on verification needs and account terms.
• Only then cancel.

Have both the developer and the person who uses the enquiries sign off the checks.

One honest caveat

No export guarantees every field, every attachment, every automation, or every permission comes across cleanly. Account setups differ, form types differ, and Wix changes features over time. Treat the steps above as a strong default workflow, verify against your own site, and check each form individually rather than trusting one blanket export. An agreed overlap period gives the team time to resolve discrepancies without rushing the account changes.