Can Kentico's custom page types and structured content be migrated to Google Sites?
No. Google Sites has no content modeling layer: no custom fields, no schemas, no typed page templates, and no API for creating them. Structured content from Kentico Document Types can be flattened into plain HTML pages, but all field definitions, type schemas, and any dynamic rendering logic tied to those types are permanently lost. If preserving your content model matters, the standard recommendation is to target a capable CMS such as WordPress, Contentful, or Drupal instead of Google Sites.
What happens to Kentico users, roles, and permissions when moving to Google Sites?
None of these migrate: Google Sites has no user database, no role objects, and no permissions layer of its own. Access control in Google Sites is limited to three fixed sharing levels (Viewer, Commenter, Editor) applied through Google Workspace, which must be configured manually in the Google Workspace Admin console after migration. Kentico user profile data and custom fields should be redirected to a companion system such as Google Sheets, a CRM, or Firebase, because Google Sites cannot store them. If user management or role-based access control is a hard requirement, Google Sites is not a suitable target platform.
Will Kentico BizForms and form submission history carry over to Google Sites?
No. Google Sites has no native form engine, no database layer, and no API capable of receiving form schema definitions or submission records. The legacy Sites API is fully deprecated. The standard approach is to rebuild forms in Google Forms (embedded via iframe in Google Sites pages) and export historical submission data from Kentico to Google Sheets as an archive. Neither step constitutes a migration into Google Sites itself; both require manual rebuilding and data export work outside the migration.
Why can't Kentico newsletters, email campaigns, or taxonomy be moved to Google Sites?
Google Sites is a static page builder with no email marketing functionality and no taxonomy or metadata system, so there is no destination object for either type of data. Kentico Email Campaign data should be redirected to a dedicated platform such as Mailchimp or HubSpot, or archived as structured CSVs in Google Drive. Kentico Categories and taxonomy can be approximated by organising Google Sites pages into sub-page folders that mimic category groupings, but all structured relationships and metadata are discarded. If categorical navigation or email marketing is central to your site, Google Sites is unlikely to be the right long-term target.
Does the Google Sites API support content import, and what does that mean for the migration?
The current Google Sites API (v1beta) is read-only and exposes no endpoint for programmatic content creation or import; the classic Sites API is fully deprecated. This means page content must be pushed through workarounds rather than a standard write API, and pages must be handled individually since there is no bulk-import endpoint. Large sites will require pagination and throttling logic to stay within Google's rate limits. This architectural limitation is a key reason why almost all Kentico content entities (structured types, users, roles, forms, taxonomy, campaigns) have no viable landing zone in Google Sites.
What needs to be rebuilt manually in Google Sites after the migration, and what will be silently lost?
Kentico Web Parts and Widgets (including navigation menus, carousels, data-bound repeaters, and form widgets) have no equivalent in Google Sites and must be manually replaced with the closest available native block (for example, a static Google Slides embed in place of an image carousel, or an embedded Google Form in place of a form widget). Multilingual content has no language-configuration object in Google Sites, so any localised variants must be duplicated as separate pages and named manually. Taxonomy relationships, workflow history, page-level permissions, and all structured metadata are lost with no recovery path. Planning these gaps explicitly before migration begins is the only way to avoid discovering them after cutover.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
