How to migrate from Wix to Payload CMS
Transfer Wix CMS collections to Payload with field and access maps. Check export scope, media and dynamic pages before switching public retail guidance.
- Published
- Last updated
You can migrate from Wix to Payload CMS by exporting the intended CMS collections, mapping their fields and importing converted records. Rebuild dynamic pages and access rules separately. Keep public retail guidance apart from private member data, because an export doesn’t carry the protections that controlled access on the Wix site.
Separate the collection move from the whole site
Start with the public editorial collections you intend to replace. A buying guide’s text is one migration object. Its dynamic-page layout and connected dataset are another. App-managed products, orders and member records have their own migration requirements.
Wix’s app collection documentation explains that apps create these collections and control changes through the relevant app. You can inspect their access settings, but those app collection permissions can’t be edited in the CMS. Exportable records don’t transfer the app’s behaviour, payments or member permissions to Payload.
A Payload move fits a team prepared to own the schema and frontend implementation. Developers configure content fields and access rules, while editors use the resulting interface. Keep Wix when its current site and editorial workflow already meet your needs and your team wants to keep managing presentation there.
Assign a content owner and an implementation owner before exporting. List the dynamic pages and services that consume each collection. Record who can export data, change domains and manage the connected accounts. Keep billing changes separate from content transfer so an early cancellation doesn’t remove a needed source or recovery option.
Export the intended collection data
Inventory the collection’s fields and IDs, record counts, reference targets and media. Record its permissions outside the CSV. Wix’s collection permissions determine who can view or change content, including distinctions between members and an item’s creator. A migration must recreate the required outcome in Payload.
If your site uses the optional sandbox, identify which version contains the approved public content. Wix’s sandbox and live collection guide explains that the versions can contain different records. Export the intended version. Keep unapproved sandbox changes separate from the live-content baseline.
Follow Wix’s CSV export procedure.
- Open CMS in the dashboard and select the collection. Use the editor to reach a sandbox collection when needed.
- If sandbox is enabled, select Sandbox Collection or Live Collection deliberately.
- Choose More Actions, then Export to CSV.
- Select The entire collection for all records and fields, including hidden and system fields. Filtered data exports only matching items. Collection fields exports field names without records.
- Export the file and record its collection, environment and chosen scope beside the expected record count.
Preserve UTF-8 encoding when opening and saving non-Latin text. Wix exports time fields as UTC+0. Record that basis in the field map, then define the destination timezone handling explicitly. Relabelling a UTC value as local time changes its meaning.
Keep an untouched export and work on a copy. Inspect actual cell values before choosing conversions, especially rich content and media references. Wix distinguishes Rich Text and Rich Content fields, so don’t assume every formatted field contains the same data structure.
Rebuild schema, references and access
Create the Payload collections from an explicit field map. Retain Wix record IDs in a dedicated source field, separate from Payload’s generated IDs. Record every intentional omission so a missing field can be distinguished from an import failure.
| Wix content | Destination value | Conversion or rebuilding work |
|---|---|---|
| Title and plain text | Text fields | Preserve characters and required validation |
| Dynamic-page path | Slug plus URL map | Rebuild route generation and redirects |
| Time field | Agreed time representation | Preserve the UTC basis and define display conversion |
| Reference or multi-reference | Relationship field | Resolve source targets to destination IDs |
| Formatted content | Selected editor format | Convert the observed source structure and inspect output |
| Media field | Upload relationship or approved asset URL | Acquire permitted files and replace source references |
| Private member fields | Separate protected collection, if separately authorised | Keep out of the public-guide import |
Choose Payload’s Import Export plugin for prepared collection data that fits its import format. Configure its required queue processing and inspect the preview. CSV acceptance doesn’t mean a Wix reference or rich-content structure has become a valid destination field.
For more involved conversions, use a developer-maintained importer through the Payload Local API. First run it against a disposable development environment with fictional or authorised non-sensitive records. Use stable source IDs to match repeat imports and report failures by source row.
Import media and independent reference targets before the records that depend on them. Store a map from source IDs to destination IDs. Then fill each relationship using Payload’s documented relationship formats. Complete circular relationships in a second pass and inspect that every target belongs to the intended collection.
For HTML that you choose to convert into Lexical, follow Payload’s HTML conversion instructions. Handle embedded images separately and connect uploaded files during conversion. Preserve the raw source alongside converted content until the rendered result is accepted.
Recreate access with least privilege through Payload access control. Give editors only the actions their role needs. Define public reads for approved guides without giving anonymous visitors access to private collections or draft fields.
Use an access matrix like this fictional example before connecting the frontend.
| Content | Anonymous visitor | Content editor | Shopping-answer source |
|---|---|---|---|
| Published buying guide | Read approved fields | Edit within assigned role | Read approved guidance |
| Draft guide | Denied | Read and edit as assigned | Denied |
| Private member record | Denied | Denied unless separately authorised | Denied |
| Internal editorial note | Denied | Read within assigned role | Denied |
Payload’s Local API access instructions state that local operations bypass access checks by default. Pass the authenticated user and set overrideAccess: false when testing permission enforcement through that API. Also inspect the frontend response, because server-side code can expose fields that an anonymous API request cannot read.
Validate dynamic pages and retail answers
Compare destination records with the approved export manifest. Check sample text and time values against the source copy. Open each reference target and confirm that images and documents load from the chosen destination. Record exclusions separately from failed rows.
In a fictional migration, eight public guides reference two categories. Expect eight destination guides with both category records available. A private member collection is outside that import and must remain absent from public delivery. The guide count alone won’t detect a broken category relationship or a private field leaked by the frontend.
Rebuild dynamic-page templates and test their actual routes. Check rendered headings, body content and links on desktop and mobile. For every changed URL, confirm that the old route redirects to the intended guide. Confirm that public delivery and its content responses deny drafts and private data with a signed-out visitor session. Repeat with each relevant editor role.
Then publish one approved guide change and follow it into shopping answers. For example, change a fictional care guide from hand-washing to machine-washing only after the retailer approves that advice. Confirm the new Payload value, the rendered guide and the document supplied to the shopping-answer service all agree.
Refresh the service’s retrieval source and ask the corresponding care question. The answer must use the approved instruction and product context. Disconnect the retired Wix source so it can’t supply the old advice. Check that private content stays excluded from the retrieval source as well as the public page.
Change over with recoverable copies
Assign domain routing, editor invitations and integration credentials as separate cutover tasks. Record previous settings before changing them. Freeze edits briefly or capture a final export so the destination includes source changes made during the rebuild. Keep the Wix site and its collections available while you validate the new delivery.
Retain exports, authorised media copies and the source-to-destination ID map. Preserve collection permissions and the URL map with them. Define who can return delivery to the original site and how approved edits made in Payload would be reconciled before that return.
Wix’s collection backup procedure restores collection content and settings. A restore overwrites later changes, including visitor submissions in the restored collections. App collections are outside these CMS backups. Choose a recovery action for the affected data only after protecting later records.
Wix site history restores the site’s presentation separately and doesn’t restore CMS collection content. Keep those recovery operations distinct. On the Payload side, enabled document versions can restore earlier content states. Keep hosting-level database and file backups for broader recovery.
If a record or relationship differs, pause its publication and compare the source row with the destination mapping. Give Wix Customer Care a redacted example for source export problems. Use Payload’s official community help for destination questions, with the relevant schema and import error. Keep recovery copies until the approved guides, access outcomes and shopping answers pass the same checks after cutover.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.