dotCMS at a glance
- Type
- Hybrid headless CMS
- Built with
- Java, with REST and GraphQL APIs
- Hosting
- dotCMS Cloud, or self-hosted
- Best for
- Organisations running many sites from one place
How dotCMS works
Content in dotCMS is made of content types, each with its own fields, and items can be shared across sites. Pages are built from templates and containers, files sit in folders on each site, the block editor holds rich text with embedded content, and workflows control who publishes what.
Who uses dotCMS
Mid-size and large organisations use dotCMS, often in finance, education and the public sector, where one team runs a group of sites. It suits teams that want editors to build pages and developers to use APIs on the same content.
What a dotCMS migration covers
When the connector is ready, Reloque will scan your dotCMS content first and map each field before anything moves. These are the kinds of content a migration has to account for.
- Content types and items
- Fields
- Sites
- Files and folders
- Pages
- Languages
What dotCMS does well
Many sites, one system
Sites share content types and items where it helps.
Pages or APIs
Editors build pages, and the same content feeds apps.
Workflows and roles
Publishing steps and permissions are detailed.
Free for smaller teams
Free to use for businesses under US$5M in total finances.
What to weigh before you move
No CMS fits every team. These are the points that come up most when people plan to leave dotCMS, or to make it their next home.
- Java to runSelf-hosting means running a Java application and its database.
- Licence by sizeCheck dotCMS's licence terms for larger organisations before you commit.
- Smaller communityFewer developers and agencies know it than the big names.
Planning a move from dotCMS
A dotCMS move centres on the content types and on which items each site shares with the others.
- List the content types, their fields and the sites that use each one
- Note items shared between sites, so each lands once
- Check files and folders on each site, and where content uses them
- Check every language, and which items exist only in some of them
Where dotCMS content could go
The dotCMS connector is planned, and connectors are built in the order people ask for them. These ten work today, in every direction, and dotCMS will join them both ways.
Moving to dotCMS
Moving to dotCMS means creating content types for each kind of content, choosing which site each item belongs to, then filling them through its API.
dotCMS questions
What is dotCMS?
dotCMS is a Java-based CMS that works both ways: it can build pages itself, or serve content through APIs to a separate front end. One installation can run many sites in many languages.
Who uses dotCMS?
Mid-size and large organisations use dotCMS, often in finance, education and the public sector, where one team runs a group of sites. It suits teams that want editors to build pages and developers to use APIs on the same content.
What content can be migrated to or from dotCMS?
A migration with dotCMS typically covers content types and their items, fields, sites, files and folders, pages and languages. Reloque scans your site first and shows what it found before anything moves.
What should I prepare before a dotCMS migration?
A dotCMS move centres on the content types and on which items each site shares with the others. Four checks help most: (1) list the content types, their fields and the sites that use each one; (2) note items shared between sites, so each lands once; (3) check files and folders on each site, and where content uses them; (4) check every language, and which items exist only in some of them.
Can Reloque migrate dotCMS today?
Not yet. The dotCMS connector is planned, in both directions with every CMS Reloque supports. Reloque moves WordPress, Payload, Strapi, Ghost, Umbraco, Drupal, Contentful, Sanity, Storyblok and Webflow today. Tell us your route when you start a free assessment.