Contentful models structured content for any channel through its API; Wix builds and hosts the actual site, with its own CMS Collections driving dynamic pages. Teams running both end up typing the same entry twice — once into Contentful’s structured model, once into a Wix Collection — and the two drift apart as soon as either side changes. This guide covers how to sync Contentful and Wix without code, in either direction.
Why sync Contentful with Wix
Contentful and Wix each do one job well, and most teams running both want the two to share data rather than duplicate it:
- Structured content in Contentful, a live site in Wix. Model content once in Contentful — with references, rich text, and reusable content types — then push finished entries into Wix CMS Collections so the site renders them with Wix’s own design and page tools.
- Multi-channel content, one Wix site as a consumer. Contentful is often the system of record feeding a mobile app, another site, or an internal tool; syncing lets the public Wix site pull from the same entries instead of maintaining a separate copy.
- Editorial handoff without manual re-entry. Writers work in whichever tool fits the workflow — Contentful’s structured editor or Wix’s Content Manager — and the sync keeps the other side current automatically.
A one-time CSV export or copy-paste pass covers a single migration moment. It breaks down once either side keeps publishing new entries or edits weekly, which is the normal state for an active content team.
What you need before you start
- A Contentful space with the content model (content types, fields, references) you want to sync.
- A Wix site with a CMS Collection shaped to mirror that content type — fields, rich text, and image fields as needed.
- A Synquake account — sign up free at app.synquake.com.
No developer, no custom Contentful app, and no Wix Velo code required. Synquake connects to the Contentful and Wix CMS APIs directly.
Step-by-step: connecting Contentful and Wix
1. Connect both accounts
Add Contentful and Wix as connections in Synquake. Contentful authorizes with a space API token; Wix authorizes through OAuth from your site dashboard. No credentials get passed around the team manually.
2. Pick what to sync
Choose the Contentful content type (e.g. Article, Product, Page) and the Wix CMS Collection you want it connected to. Most teams start with one content type, then add more once the mapping is confirmed.
3. Map fields visually
Draw the connections between Contentful fields (short text, rich text, references, media) and the matching Wix Collection fields (text, rich text, reference, image). Field types don’t need to match exactly up front — Synquake handles the conversion, including Contentful rich text rendering into Wix’s rich content field.
4. Choose sync direction
Pick one-way (Contentful → Wix, the common case when Contentful is the system of record) or two-way sync, so an edit made on either side pushes to the other automatically. Two-way sync is included on every Synquake plan, not a paid upgrade.
5. Preview before going live
Run a preview sync against a handful of real entries first. Confirm rich text formatting, references, and images land correctly in the Wix Collection before enabling continuous sync.
6. Turn on live sync
Once the preview checks out, enable scheduled or real-time sync. From here, a new Contentful entry or edit flows into the matching Wix CMS item automatically, with no manual copy-paste step.
Common Contentful–Wix sync scenarios
- Marketing site on Wix, content modeled in Contentful. Editors manage structured entries in Contentful; the Wix site renders them through CMS Collections without anyone touching the Wix Editor for routine content updates.
- Multi-channel publishing. The same Contentful entries feed a mobile app or another site alongside the Wix site, all from one source of truth instead of several manual copies.
- Migrating off Wix-only content. Teams moving structured content into Contentful for better modeling can sync it back into Wix during the transition, so the live site stays current while the migration is in progress.
- Localized content. Contentful’s locale fields can sync into separate Wix Collection items per language, keeping translated pages aligned with the source entries.
Avoiding common sync problems
- Reference fields: Confirm how Contentful’s linked entries map to Wix’s reference fields before enabling two-way sync — a reference pointing to an entry that hasn’t synced yet is the most common cause of a missing link on the Wix side.
- Rich text formatting: Preview a few entries with embedded links, lists, and images to confirm Contentful’s rich text converts cleanly into Wix’s rich content field rather than losing formatting.
- Duplicate items: Set a stable matching field (a Contentful entry ID or slug) so re-running a sync updates the existing Wix CMS item instead of creating a new one.
- Collection item limits: Wix CMS Collections cap the number of items per site plan — check that limit against your Contentful content volume before syncing an entire space in one pass.
Beyond Contentful and Wix
Synquake’s sync is any-to-any across nine platforms — Airtable, Webflow, WordPress, Supabase (including Lovable-built apps), Wix, Shopify, Squarespace, Google Sheets, and Contentful — plus CSV import (a source, never a destination) on every plan. The same Contentful space you sync with Wix can also feed an Airtable base for editorial planning, or a Google Sheet for reporting, without building a separate integration for each. See the full integrations page for details, or read how it works for the connection, mapping, and monitoring model.
Related reading
- How to Sync Contentful and Webflow Without Code
- How to Sync Wix and Webflow Without Code
- How to Sync Wix and Airtable Without Code
Get started
Syncing Contentful and Wix without code removes the manual re-entry step between structured content and a live site. Start your first Contentful-to-Wix sync free and preview it against real entries before going live.