Getting started
Migrating your content
Moving from Contentful does not mean rebuilding your model by hand. Export the space as JSON, upload it once, and CloudSource recreates the lot.
One-step import. Export your Contentful space as JSON, upload it via Tools → Import, and review the summary before anything is written.
What gets imported
CloudSource reads your export file and recreates everything in the target space.
Models
Contentful content types become CloudSource models, with every field mapped to its closest equivalent.
Assets
Every media file is downloaded from Contentful and re-uploaded into your own S3 bucket.
Content
Entries are recreated with all references resolved, and can be auto-published if you want.
How to import
- Export from Contentful In Contentful, go to Settings → Export and export your space as JSON.
- Pick the destination space In CloudSource, switch to the space you want the content to land in. Importing into a fresh space keeps the blast radius small.
- Open Tools → Import Upload the JSON file you exported.
- Review the summary Check the counts of models, assets and entries, and how each field type has been mapped. Nothing is written until you confirm.
- Click Import Assets are fetched and re-uploaded as part of this step, so a large media library takes longer than a large content set.
Field type mapping
Contentful field types are converted automatically. This is the complete mapping.
Contentful → CloudSource
| Contentful | CloudSource |
|---|---|
| Short text | text |
| Long text | textarea |
| Rich text | richtext |
| Number / Integer | number |
| Boolean | boolean |
| Date | date |
| Media (single) | media |
| Media (multiple) | media_multiple |
| Reference (single) | relation |
| Reference (multiple) | relation_multiple |
Types with no direct equivalent. Location fields, arbitrary JSON objects, and rich text containing embedded entries do not map one to one. Check the import summary carefully for these, and decide how you want to represent them before you commit.
Planning the wider move
The content import is the quick part. Budget your time around the rest of it.
| Stage | Typical effort | Notes |
|---|---|---|
| Import content | Minutes to hours | Driven by media volume rather than entry count. |
| Check the model | An hour or two | Spot-check entries against the originals, especially rich text and relations. |
| Update the storefront | Days to weeks | The real work. Response shapes differ, so every read needs updating and testing. |
| Run both in parallel | Weeks | Keep the old subscription until you are confident, then cancel at renewal. |
| Retrain editors | A morning | Concepts carry over directly. This is rarely the bottleneck. |
Import twice. Do a throwaway import into a scratch space first, purely to see what the summary says about your model. Then create the real space and import again with the decisions already made.