Scroll Viewport
Scroll Viewport
Breadcrumbs

Viewport to Scroll Sites: Upgrade FAQ

This FAQ answers recurring upgrade questions and highlights practical checks that are easy to miss.

Moving from Scroll Viewport to Scroll Sites creates a new site that eventually replaces your existing Viewport site.

Important: Scroll Viewport reaches end of service on . Updates to existing Viewport sites have already been stopped. See the upgrade timeline and start with How to upgrade to Scroll Sites.

Before You Start

Preparation makes the difference between a calm cutover and a rushed one. Before you review your new site, we advise you to check the following:

  1. Inventory your domains, redirects, custom code, theme assets, integrations, and access settings. Save copies outside Viewport.

  2. Pick a low-risk window to review and test. Your Viewport site stays live throughout preparation.

  3. Keep your Viewport site available until the new site is live and every check in this article passes.

Will My Live Viewport Site Go Offline While I Prepare Scroll Sites?

No. Your replicated Scroll site is created in an unpublished state on a temporary domain, so you can review it privately. Your Viewport site keeps serving traffic the whole time.

The domain transfer and final cutover happen only when you choose Complete upgrade. For the full sequence, see Automatically Replicate a Scroll Viewport Site as a Scroll Site.

Does My New Scroll Site Stay Up To Date With The New Content I Publish in Confluence?

Yes. Your Scroll site is not a frozen snapshot of the day it was created. It keeps reading content from your Confluence content sources, so edits you make while preparing the upgrade are picked up.

How quickly they appear depends on your update strategy, which you set under My Sites > [your site] > Site Settings > Update Strategy:

  • Live updates: changes in Confluence appear on your site automatically, usually within 30 seconds to five minutes. Changes to site settings still need a manual update.

  • Manual updates: changes stay pending until you select Update site, which shows a count of everything waiting to publish.

For both options, see Update a Site.

Custom Domains

Can I Keep My Existing Viewport Domain?

Yes. The upgrade wizard transfers your domain and site access settings without downtime, automatically. Your domain can't be connected to both products at the same time, so finish your content and settings review before you start the transfer.

Don't change domain or other site settings while the transfer runs. Changes made during the transfer break the automatic domain handover.

For details, see How to Move a Custom Domain From One Viewport Site.

What Should I Do if Domain Validation or SSL Stays Pending?

Check your DNS records first. Two things are needed:

  1. Confirm both CNAME records exist, one for custom domain validation and one for certificate validation.

  2. Confirm your CAA records allow AWS Certificate Manager to issue a certificate for your domain or subdomain.

Validation is automated and can take several hours. If the CNAME records can't be found within 72 hours, the process fails and has to be restarted. Keep the records in place for as long as you use the domain.

For the full setup, see Connect a Custom Domain.

Can I Delete My Old Viewport Site After Upgrading?

Only once your Scroll site is live on the intended domain, your content and redirects are verified, and access protection behaves as expected.

Deleting a Viewport site can't be undone. Keep copies of your CSS, JavaScript, redirect rules, and theme assets before you delete anything.

Review Your New Site

Why Does My Upgraded Site Look Different, Especially the Banner and Colors?

The Scroll Sites Help Center theme isn't identical to the Viewport theme, so some visual differences are expected. Common ones include banner positioning, fonts, component sizing, and the removal of portal and content-source icons.

Your brand colors and assets aren't always carried across either. To review them:

  1. Open your temporary Scroll site and your live Viewport site side by side.

  2. Go to Site Settings > Look and Feel > Customize theme.

  3. Work through every tab, checking each color setting and upload field.

  4. Re-upload any missing logos, icons, and banners. Assets can missing when they use a file format Scroll Sites doesn't support. See "Why do I see 'Couldn't migrate theme customizations' during the upgrade?"

To change your header color, go to the Sections tab and set Background color under Header. Adjust Text color there too, so your header text stays readable. For the full range of options, see Customize Site Logo, Header, Footer, and Favicon.

How Do I Confirm My New Site Has My Latest Viewport Content?

Compare your temporary Scroll site against your live Viewport site, starting with the pages you edited most recently.

Then open My Sites > [your site] > Site updates. The table lists published and pending changes, with a Time published column you can check against your edit history.

If something is missing, see My Latest Change Doesn't Appear in the Live Site. Some changes, such as renaming a space or editing a link URL, only publish when combined with other changes. As a last resort, follow Manually Trigger a Full Site Update.

Reapply Your Customization

What Happens to My Custom CSS, JavaScript, Redirects, and AI settings?

These settings aren't always copied automatically, so plan to reapply them:

  • Redirects: copy your rules into Site Settings > Redirects.

  • Custom CSS and JavaScript: copy your code into the theme configurator, then review it. The markup differs between products, so your selectors need checking.

Scroll Sites renamed several attributes and tokens. For example, data-vp-component is now data-component, and the vpt prefix has been dropped from theme tokens, so --vpt-theme-text-font is now --theme-text-font. Deprecated tokens have been removed entirely.

For the full list of changes, see Migrate Custom Code From Scroll Viewport to Scroll Sites.

Custom code modifications sit outside the scope of K15t support and can change your site in unexpected ways. We recommend having someone comfortable with web development apply and maintain them.

Troubleshoot Content and Links

Why Are Links, Excerpts, Attachments, or Diagrams Broken After the Upgrade?

Use your site issue report as an upgrade checklist. Go to My Sites > [your site] > Site issue report to see errors, warnings, and suggestions from your site updates, each linked to the affected page.

A Linked content not found warning usually has one of these causes:

  • The target page isn't part of a published content source.

  • The link points to a draft, often visible as createpage.action? in the path.

  • The relevant Scroll Documents version or variant isn't included in your site.

Fix it by relinking to published content, or by adding the target to your content source. Then verify missing files and test third-party macros one at a time.

For more, see Resolve Site Issues and Linked Content Not Found.

Your site issue report keeps a history, so resolved issues from earlier updates may still be listed. Focus on issues from your most recent update.

Legacy article URLs in the /page-title.12345678.html format aren't supported in Scroll Sites, but redirects for them are created automatically during the upgrade.

Don't assume every pattern is covered. Bare ID paths, custom patterns such as /kb/{id}.html, and application-specific URLs may need explicit redirect rules. Test a representative sample of your most important URLs before cutover, then add the rules you need.

For links you embed in products, QR codes, or other places you can't easily edit later, use context keys. They stay valid when your content moves. See Generate Stable Links (Context Keys).

What Should I do If My Upgrade is Stuck, Fails, or Shows An Error?

Don't change settings repeatedly or start parallel upgrades, as this makes the problem harder to diagnose.

Instead, collect this information:

  • Your site URL and Confluence base URL

  • The upgrade step you were on

  • The exact error message and any incident ID

If your site is stuck during generation, transfer, or Complete upgrade, contact K15t support with those details. For update failures, start with Resolve Site Issues.

Why Do I See "Couldn't Migrate Theme Customizations" During the Upgrade?

If the upgrade wizard "Couldn't migrate theme customizations," or an error starting with "Asset must have one of the following content types," it means that your Viewport theme uses an image format that Scroll Sites doesn't support.

Scroll Sites supports these formats for theme assets such as your logo, favicon, and banner: PNG, JPEG, GIF, WebP, AVIF, SVG, and ICO.

We recommend you continue the upgrade without theme customization. Complete the upgrade, then add your logo, favicon, and banner in Scroll Sites. Go to Site Settings > Look and feel > Customize theme.

If you'd rather use your customizations instead, save a copy of the unsupported assets, replace or delete them in the Viewport theme editor, and run the upgrade again.

To reuse an asset that's in an unsupported format, convert it to PNG or SVG before you upload it.

Final Validation

What Should I Check Before I Call the Upgrade Complete?

Work through this list before you retire your Viewport site:

  • Your intended domain resolves with a valid certificate.

  • Site access works for anonymous, token, and SAML users, as applicable to your setup.

  • Pages, navigation, search, images, downloads, and diagrams all work.

  • Your old Viewport URLs and critical in-app links have been tested.

  • Your custom code, theme assets, and update strategy have been reviewed.

  • Your site is published successfully, and your Viewport site is no longer needed.

Last updated: