--- version: "v4" language: "en" --- # Scroll Apps Migration Hub ## Scroll Apps Migration Hub Smoothly transition from Scroll Versions and Scroll Translations to the next generation app: Scroll Content Manager [Let's begin](https://migration.k15t.com/scroll-apps/migration/introduction.md) ### Latest News * #### [Support for K15t Data Center Apps After March 2029 -August ´26](https://migration.k15t.com/scroll-apps/migration/support-for-k15t-data-center-apps-after-march-2029-august-26.md) August 11, 2026 * #### [A Better Health Check Experience in Conversion Process- July ´26](https://migration.k15t.com/scroll-apps/migration/a-better-health-check-experience-in-conversion-process-july-26.md) July 30, 2026 * #### [Cancelling Conversion Process is Now Possible - June '26](https://migration.k15t.com/scroll-apps/migration/cancelling-conversion-process-is-now-possible-june-26.md) June 23, 2026 ### The Migration Phases * #### [Understand](https://migration.k15t.com/scroll-apps/migration/understand.md) Learn about the next generation of Scroll Apps and how to start using them on Cloud or Data Center. * #### [Assess](https://migration.k15t.com/scroll-apps/migration/assess.md) Evaluate your current use of the Scroll Apps to understand how to transition to the next generation apps. * #### [Prepare](https://migration.k15t.com/scroll-apps/migration/prepare.md) Prepare yourself and your Confluence spaces for the conversion to Scroll Content Manager. ### Articles * #### [Introduction](https://migration.k15t.com/scroll-apps/migration/introduction.md) #### [Understand](https://migration.k15t.com/scroll-apps/migration/understand.md) #### [Assess](https://migration.k15t.com/scroll-apps/migration/assess.md) #### [Prepare](https://migration.k15t.com/scroll-apps/migration/prepare.md) #### [Convert](https://migration.k15t.com/scroll-apps/migration/convert.md) #### [Conversion and Migration Knowledge Base](https://migration.k15t.com/scroll-apps/migration/migration-faq.md) #### [Troubleshooting](https://migration.k15t.com/scroll-apps/migration/troubleshooting.md) #### [Latest News](https://migration.k15t.com/scroll-apps/migration/latest-news.md) --- version: "v4" language: "en" --- # A Better Health Check Experience in Conversion Process- July ´26 Starting with **Scroll Versions 4.8.13**, we've given the health check step in the conversion process a face-lift, making it easier to understand and act on before you proceed with the conversion. ## Clearer categorization Health check results are now organized into three clear categories, so you know exactly what needs your attention: * **Errors** -- issues that must be fixed before conversion can proceed * **Warnings** -- items that require a decision on your part * **Suggestions** -- recommendations to help you get the best results ![Screenshot 2026-07-30 at 13.25.20.png](https://migration.k15t.com/__attachments/a_0707b19bf113dfa9d640140a9f039d43b97115632089b44ccba562ee8c6fe42e/Screenshot%202026-07-30%20at%2013.25.20.png?cb=02ed90765f6ca2a2752a0b5b787ae930) Health checks are categorized to easily see what requires attention ## Download what you need You can now download health check results by category, or all at once, depending on what's most useful for your conversion workflow. ## Focused, actionable export The downloaded .csv file only includes information that's relevant to you, along with direct links to our Help Center for each check, guiding you step by step on how to resolve any issues. ![image-20260730-110107.png](https://migration.k15t.com/__attachments/a_350aa0636b262675353cdd88169c88341e73cec94b2125ed53a8683f7a2fae0f/image-20260730-110107.png?cb=94433371593c7a0e6e401da55bd9ddf4) Improved health check file contains direct links to instructions ## Health check is mandatory Passing the health check remains a mandatory step in the conversion process. A conversion can only be started once a passed health check newer than 7 days is on record, ensuring the content you convert meets your expectations every time. In rare cases, for example, if passing health checks is blocked due to an issue on our side, or if you'd simply like to preview the conversion experience before your health check is fully resolved, an override is available. This isn't intended for routine use; if you find yourself needing it, please reach out to our [support team](https://customer.support.k15t.com/servicedesk/customer/portal/35), who can advise on the best path forward. --- version: "v4" language: "en" --- # A Smoother Way to Handle Space Reindexing - Mar '26 We're excited to introduce an improvement that makes your Confluence space conversion process more flexible and predictable. Previously, space reindexing was a built-in and mandatory part of the conversion process. While this worked well for smaller spaces, larger spaces could experience long indexing times. In some cases, the process appeared to get stuck for hours, with little visibility into when it would move forward. With our latest release, Scroll Versions 4.8.7, indexing is no longer embedded directly into the conversion flow. This change gives you better control over when indexing happens, helping you better plan and manage your conversion / migration workflow. Once your space conversion is complete, you'll be prompted to choose whether to start indexing immediately or postpone it to a more convenient time. ![image-20260319-053226.png](https://migration.k15t.com/__attachments/a_8a4a895a7e328e4d885faff1e6dbee1b424af248e996ce636851f172ea629e88/image-20260319-053226.png?cb=c6827e9ca8395e6de412a04210a7667d) You can trigger reindexing at the end of the conversion You'll also see an option within the converted space to trigger indexing whenever you're ready. ![image-20260319-053429.png](https://migration.k15t.com/__attachments/a_41752f708110ded22a17e24e04017b05f681d709b319077d12107f1db42fee96/image-20260319-053429.png?cb=2f7e5395fee83da93f38dba31768145f) You can also trigger reindexing from the target space's post actions It's important to note that indexing is still a required step before migrating your space to the cloud. However, by making it a separate action, you can now avoid unnecessary delays during conversion and decide the best time to run it. This update is designed to give you a smoother, more transparent experience especially when working with large spaces. --- version: "v4" language: "en" --- # All Paid K15t Cloud Apps Are Now Cloud Fortified - Dec'22 ![Blog-Post-Share_Image_Cloud-Fortified-Apps.png](https://migration.k15t.com/__attachments/a_76c176d10c7de986721d4c4356ef49c09f4eaef91106fb300af9e1ecf871f407/Blog-Post-Share_Image_Cloud-Fortified-Apps.png?cb=f1e3bf4bf0275e8da6fff66ca510d68e) It doesn't matter whether it's Confluence or Jira on Cloud, the product development at K15t has always had the highest standards, and the same applies to our customers. Security, reliability, and accessible support is always the highest priority for our apps while enabling customers to customize Atlassian products as per their requirements. **And now we have made it official, as we're proud to announce that all K15t paid Cloud apps have the Cloud Fortified badge from Atlassian!** ## What Is an Atlassian Cloud Fortified Badge? The Atlassian Cloud Fortified Apps Program guides large customers and those with more business-critical operating requirements when it comes to Cloud apps on the Atlassian Marketplace. All apps on the Atlassian Marketplace need to meet certain eligibility requirements of enterprise readiness to apply for the Cloud Fortified Badge. These include participation in: * **Security programs:** * [Marketplace Security Bug Bounty Program](https://developer.atlassian.com/platform/marketplace/marketplace-security-bug-bounty-program/) * [Security Self-Assessment Program](https://developer.atlassian.com/platform/marketplace/security-self-assessment-program/) * **Reliability programs:** * Core capability Service Level Objectives (SLOs) and tests * Incident management * **Support programs:** * Provide a support point of contact * Respond to a critical, high-severity support ticket within one day (24 hours), 5 working days a week in the Marketplace Partner local timezone ### Which K15t Apps Are Cloud Fortified? Continuing the tradition of being at the forefront of customer oriented offerings, all K15t apps are now Cloud fortified. **Apps for Confluence Cloud** * [Scroll Documents](https://marketplace.atlassian.com/apps/1217608/scroll-documents-for-confluence?hosting=cloud&tab=overview) * [Translations for Scroll Documents](https://marketplace.atlassian.com/apps/1227238/translations-for-scroll-documents?hosting=cloud&tab=overview) * [Variants for Scroll Documents](https://marketplace.atlassian.com/apps/1226295/variants-for-scroll-documents?hosting=cloud&tab=overview) * [Scroll Viewport](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview) * [Scroll PDF Exporter](https://marketplace.atlassian.com/apps/7019/scroll-pdf-exporter-for-confluence?hosting=cloud&tab=overview) * [Scroll Word Exporter](https://marketplace.atlassian.com/apps/24982/scroll-word-exporter-for-confluence?hosting=cloud&tab=overview) * [Scroll HTML Exporter](https://marketplace.atlassian.com/apps/420604/scroll-html-exporter-for-confluence?hosting=cloud&tab=overview) * [Scroll ImageMap](https://marketplace.atlassian.com/apps/253/scroll-imagemap-for-confluence?hosting=cloud&tab=overview) * [Orderly Databases](https://marketplace.atlassian.com/apps/1227131/orderly-databases-for-confluence?hosting=cloud&tab=overview) **Apps for Jira Cloud** * [Backbone Issue Sync](https://marketplace.atlassian.com/apps/1215199/backbone-issue-sync-for-jira?hosting=cloud&tab=overview) **Convinced? Try our Cloud Fortified Apps for free!** [++Check them out++](https://marketplace.atlassian.com/vendors/7016/k15t) --- version: "v4" language: "en" --- # Assess As you progress in your conversion journey, you are now entering the assessment phase. If you've reached this stage, you have understood the differences between Scroll Content Manager and Scroll Versions / Translations and have made an informed decision to transition to Scroll Content Manager. During the assessment phase, you will: 1. **Evaluate your current app usage:** Examine how you are currently using Scroll Versions and Scroll Translations. 2. **Determine the right timing for conversion:** After assessing how you are using the legacy apps, you should consider whether your specific use case and setup align with Scroll Content Manager. If your requirements are not entirely met, you may want to consider postponing the conversion for the time being and [letting us know about your blockers](https://support.k15t.com/cloud-migration-questions). 3. **Gain insight into feature conversion:** Get a clearer understanding of what will happen with specific features from the legacy apps when transitioning to Scroll Content Manager. The Assess phase is a critical step in ensuring a successful transition, allowing you to make informed decisions regarding your conversion. By assessing your current state and understanding how your existing features will transition, you are laying the groundwork for a seamless move to Scroll Content Manager. ## The Goal of This Phase By the end of this phase, you will have gained a deeper understanding of how your previous setup with the legacy apps translates into Scroll Content Manager. You will also be able to determine whether now is the right time for you to transition to Scroll Content Manager. To gain these insights: * **Read the articles** :The articles in this section will guide you in assessing your current setup and usage of Scroll Versions and Scroll Translations. You'll also discover how to execute and interpret the migration report. These articles also provide valuable insights into how specific features differ when converting to Scroll Content Manager. * **Run the Migration Report:** Running the migration report offers insight into the spaces you are about to convert, as well as their specific configurations and use of features. ## Next Steps Before running the migration report and assessing your current app usage, start by reading the articles below: * [The Migration Report](https://migration.k15t.com/scroll-apps/migration/run-the-migration-report.md) * [Conversion with Master Spaces](https://migration.k15t.com/scroll-apps/migration/convert-a-master-space.md) * [Conversion with Target Spaces](https://migration.k15t.com/scroll-apps/migration/convert-a-target-space.md) * [Conversion with Conditional Content](https://migration.k15t.com/scroll-apps/migration/convert-with-conditional-content.md) * [Conversion with Duplicate Page Titles](https://migration.k15t.com/scroll-apps/migration/conversion-with-duplicate-page-titles.md) * [Conversion with Include Libraries](https://migration.k15t.com/scroll-apps/migration/conversion-with-include-libraries.md) * [Migration of Incoming Links](https://migration.k15t.com/scroll-apps/migration/migration-of-incoming-links.md) --- version: "v4" language: "en" --- # Cancelling Conversion Process is Now Possible - June '26 Converting a space to Scroll documents now includes a cancel option in the progress bar, giving you a way out if the process takes too long or gets stuck. Previously, if a Scroll documents conversion was running and you needed to stop it, the only option was to restart Confluence entirely. This was disruptive and far from ideal, especially Confluence instances that were highly active. With this improvement, you can cancel an ongoing conversion directly from the progress bar, without need to restart Confluence. ![Screenshot 2026-06-23 at 15.35.38.png](https://migration.k15t.com/__attachments/a_d9453882cd8ab5c8bf127f96ca35f9894731f232899f6e0a6aba9a19a543f6e9/Screenshot%202026-06-23%20at%2015.35.38.png?cb=15ab380329d0b996fade03f9f654d32b) Cancelling is possible from the conversion progress bar ![Screenshot 2026-06-23 at 15.35.58.png](https://migration.k15t.com/__attachments/a_b81f7194952fe7dc940a82e68e03370465ef3a9d68acece993aaf41c1c7fb143/Screenshot%202026-06-23%20at%2015.35.58.png?cb=c26d447a731691a311ff7fc2770d618c) **One thing to keep in mind:** the conversion process creates the new space immediately when it starts, not when it finishes. This means if you cancel mid-way, a partially converted space will already exist in your Confluence instance. You will need to delete it manually before retrying the conversion or discarding it altogether. --- version: "v4" language: "en" --- # Categorize the Pages Does your documentation space contain several top-level pages? This might indicate that some pages belong to your official documentation, while others are internal management pages or used for content reuse. If you notice multiple top-level pages, or already know your space contains pages you don't want to include in your official documentation, we recommend reviewing and categorizing these pages accordingly. ## Label Pages Based on Their Use In a documentation space, pages typically fall into three main categories. When converting your space to Scroll Content Manager, it's important to identify which versions and pages should be included in the new structure. If some pages serve different purposes, you may want to handle them differently during the conversion. To support this, we recommend categorizing your pages using specific page labels. Here are our definitions and suggestions: | **Page category** | **Definition** | **Label** | **Page tree structure after conversion** | |---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Documentation Pages | These are the pages that constitute your official documentation. They are essential for communicating information to your audience and typically don't require any special labels. | no label | Pages without any special labels will be converted as part of your versioned Scroll Content Manager documentation. | | Included pages | These are pages included within the same space, often used for content reuse. To identify them, we suggest labeling them with "vsndoc-include-library". This does not have to be done for pages included through [Scroll Versions and Scroll Translations Include Library feature](https://migration.k15t.com/scroll-apps/migration/reuse-versions.md). | vsndoc-include-library | For pages dedicated to content reuse, we recommend placing them at the same level as your Working version, outside of your document. This can be achieved by labeling them with "vsndoc-include-library" and selecting the option"Resolve (Excerpt) Include macros across all saved versions" during conversion. | | Management pages | These pages are used for internal management purposes, such as displaying open tasks, organizing content by label, etc. To differentiate them, we recommend labeling them with "vsndoc-no-documentation". | vsndoc-no-documentation | Pages used for internal purposes, like reports, are recommended to be converted into the Working version of your document. After conversion, you can move them outside of your document. To achieve this, add the "vsndoc-no-documentation" label to these pages and uncheck the option "Migrate 'vsndoc-no-documentation' labeled page trees to all saved version" | ## How to Apply the Page Labels When labeling pages, the process differs based on whether the page is versioned or unversioned, or if it's a standard Confluence page. If you have a page tree of reused pages or management pages, it is sufficient to place the label on the parent page of that page tree. For unversioned or normal Confluence pages: * Navigate to the single page or parent page of the page tree and apply the relevant label. For versioned pages managed by Scroll Versions: 1. Navigate to the relevant page. 2. Click on the page tools icon (•••) \> select **View in Hierarchy**to access the reorder page tree. The selected page, along with its master page and dot pages, should appear unfolded. 3. Click on the master page to access the Public view, see screenshot below for reference: ![master-versioned-page.png](https://migration.k15t.com/__attachments/a_9db721733f60df04102922b108faeb0cec7ecd251fd5ef303048855d381470b1/master-versioned-page.png?cb=26afaf3e6011482f9b192648253fc6c8) 4. Click on the label icon. 5. Type in the label name and click **Add.** This approach ensures that your documentation is organized efficiently and that only relevant content is included in your new document. --- version: "v4" language: "en" --- # Cloud Roadmap and First Migration Prototype - Feb'21 First of all, we want to wish you and everyone around you a great 2021 in which we all start to see light at the end of the tunnel of the pandemic. The product teams at K15t are working in full swing in order to bring our professional technical communication solutions to Confluence Cloud. We know that the journey to Cloud isn't a simple one for many teams -- ourselves included -- but we are fully committed to getting you there. This won't happen overnight, but in the spirit of transparency and one of our core values: Be Fair, Be Frank, we will share regular updates about our progress to make sure you're able to plan for your Cloud journey in good time. Updates will be shared as news here on the K15t Cloud Migration Hub in blog posts like this. In addition, if you would like to receive these updates directly in your email inbox, [subscribe here](https://migration.k15t.com/scroll-apps/migration/latest-news). ## An Overview of Our Cloud Plans Our primary focus in 2021 is the shift to Cloud. In the past year, [**Scroll Documents**](https://marketplace.atlassian.com/apps/1217608/scroll-documents-for-confluence?hosting=cloud&tab=overview) has taken the lead as our primary app for content management and technical communication on Confluence, and we will continue to add support for Scroll Versions and Scroll Translations use cases throughout this year and beyond. In short, here's what we are working on right now: * We are preparing Scroll Documents to support advanced content management functionality similar to Scroll Versions. After the ground work is done, we'll first implement Variants and then Translations shortly after. * As far as migration is concerned, we have developed an internal prototype to convert Confluence content from a Scroll Versions-managed space into a versioned Scroll Document. Going forward, we'll work to implement migration support for features as they're released in Scroll Documents. [**Watch the video here**.](https://www.loom.com/share/b384ae39cfa4427fad732cb7ed779831?t=0) * As for our content presentation apps -- Scroll Viewport and the Scroll Exporters -- we'll make sure to make their integrations with new Scroll Documents features as seamless and immediate as possible. ### Track Progress and Get Involved For an overview of these plans, please take a look at our Cloud roadmap. It tracks all the main pieces of our Cloud solution, complete with ETAs and Jira issues to watch. Want to get involved? We'd be happy to work with you directly. Sign up for early beta testing for our Migration Tool by reaching out to [help@k15t.com](mailto:help@k15t.com). We understand that this won't be a simple transition for many of you, but we want to assure you that we will bring our same powerful solutions to the Cloud and we'll be with you every step of the way. Cheers, and see you in the Cloud! The K15t team. #### Want to discuss your Cloud migration? Our support team is happy to help! [Get Migration Support](https://support.k15t.com/tech-support) --- version: "v4" language: "en" --- # Compare, Track, and Review Versions and Variants In this article, we'll explore and compare the differences in how you can manage content authoring and review processes using Scroll Versions and Scroll Content Manager. ## Author and Review Process with Scroll Versions Scroll Versions offers the following authoring and review features: * **Built-in workflow:**Manage the status of pages within a version. You can track content progress across various stages and ensure consistency throughout the documentation lifecycle. * **Integration with Comala Document Management:** Use the [Comala Document Mgmt for Scroll Versions](https://marketplace.atlassian.com/apps/1216055/comala-document-mgmt-for-scroll-versions?hosting=server&tab=overview) extension app for advanced, customizable workflows. * **Reporting tools:**Access reports on workflows, space content, and version comparisons when comparing content across different published spaces and versions. ## Author and Review Process with Scroll Content Manager Scroll Content Manager also includes its own built-in workflow with two workflow options: * **Simple workflow** : A two-step workflow where pages can have the statuses **Draft** and **Approved** * **Approval workflow** : A three-step workflow where pages can have the statuses **Draft** , **In Review** , and **Approved** To learn more about the Scroll Content Manager's workflow feature, see:[Manage Page-level Workflows](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-workflow-intro&version=latest&variant=default) Additionally, Scroll Content Manager offers the following built-in tools to support the authoring and review process. * [Compare versions](https://help.k15t.com/scroll-docs?contextKey=k15t-docs-compare-versions&version=latest&variant=default): Compare different versions of a document. * [View activity:](https://help.k15t.com/scroll-docs?contextKey=k15t-docs-help-view-activity&version=latest&variant=default) Track the activity and changes made to a document. * [Version restrictions](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-help-permissions&version=latest&variant=default): Control access and editing permissions for specific document versions. * [Workflow report](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-view-and-set-workflow-statuses&version=latest&variant=default): Get an overview of the workflow status of all pages within a version. To learn more about how to best use these features in Scroll Content Manager, we recommend checking out our use case articles: * [Create and Manage Product Documentation in Confluence](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) * [Create and Manage Modular Product Manuals in Confluence](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-manage-modular-product-manuals&version=latest&variant=default) * [Create and Manage Company Guides, Manuals, and Employee Handbooks in Confluence](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-manage-company-guides-manuals-and-handbooks&version=latest&variant=default) * [Create and Manage Process Documentation in Confluence](https://help.k15t.com/scroll-docs/?contextKey=create-and-manage-process-documentation&version=latest&variant=default) --- version: "v4" language: "en" --- # Conditional Inline Macros with Elements If your source space (Scroll Versions enabled) had pages with inline conditional content macros that include elements such as images, the blocks containing these macros will be transformed to conditional content legacy block macros with one being tagged as "fallback" during conversion. ## What is a fallback macro? The fallback macro ensures that content that was unconditional in Scroll Versions is not lost during conversion and remains in every variant in Scroll Content Manager, even if a new variant is created in Scroll Content Manager. Unconditional content is part of the text that is not tied to any specific variant, but is always shown. We recognize that this approach may not provide the ideal user experience, but it represents the most effective workaround available within the current limitations of the Confluence Cloud editor. ## Example 1. In Scroll Versions an inline conditional content macro stores content that should be shown for the defined variants only. In the macro settings it is selected to be "displayed inline". The text above or below the macro is considered as unconditionalized content, meaning, it is shown for all variants. ![image-20251119-133805.png](https://migration.k15t.com/__attachments/a_d0f442b53f52153d15bfe9b798fa09fb9af86e622e14baa4120c6478e53d16b8/image-20251119-133805.png?cb=81eea108fb0eec6d8082b3485e71fcde) Inline conditional content macro in Scroll Versions 2. After a conversion to Scroll Content Manager the whole block is wrapped in a legacy block macros for each variant, containing the content which would have been displayed for that variant. The unconditionalized part of the block is also wrapped in a legacy block macro, so that it can be shown for the reader when no matching variant has been selected or when a new variant is created. This is achieved by flagging the macro containing the unconditionalized content as "fallback". ![image-20251119-134417.png](https://migration.k15t.com/__attachments/a_582f595be29117d1b7824e64e9819b9f665a1fe2b8ba1fe358d55f8d28c6f01f/image-20251119-134417.png?cb=92a78c0dc2767a5a76f3581c11392edf) Conditional content legacy block macros with fallback in Scroll Content Manager 3. In the editor the same block containing conditional content macro is duplicated. One block shows unconditionalized content + conditionalized content. The other block shows only unconditionalized part. The macros representing the same block from Scroll Versions are grouped together by an ID. ![image-20251119-134224.png](https://migration.k15t.com/__attachments/a_943900bde1276ebbad3a7610a61bd3bbbacf6fc592615d54a197042fb23749d6/image-20251119-134224.png?cb=9dc21d95e5de7e5de55aca48e8123d20) Inline conditional content macro in Scroll Content Manager after conversion When content is published with Scroll Exporter, Word or Scroll Sites apps, the user experience is the same as before. Content is shown based on which variant user has selected. ## FAQ ### **Can I find pages which will have the legacy block macro?** You can first find spaces which will have this legacy block macro by running Space Analysis (**General configuration \> Scroll Conversion \> Space analysis).** By choosing to show**Show more details**, you will see a column "Conditional Content Blocks". By running a space health check (**Space Tools \> Scroll Add-ons \> Health Check**) in that space you can find affected pages. We report M04 violation if there are pages where legacy block macros will be added. This is for information only and won't require any actions. ![image-20251119-123714.png](https://migration.k15t.com/__attachments/a_0219cdfd36fe386dd893f5bf8642449bae14ae1a8cc91f11d6974bd327e3173f/image-20251119-123714.png?cb=e52dba6802e690299cff20294395f306) Health check on space level shows impacted pages ### Why I do not find Scroll Conditional Content Legacy Block Macro from the macro list? The macro is only generated by conversion process, it is not a macro that should be used to create new content. Use instead Scroll Conditional Content and Scroll Conditional Content Inline macros in Scroll Content Manager. ### Can I convert Scroll Conditional Content legacy macro block to a normal macro? You can re-write sections that include conditional content by using the Scroll Conditional Content and Scroll Conditional Content Inline macros. However, there is no straight forward way of doing this, as it requires you to restructure your content to match the limitations of the Scroll Conditional Content and Scroll Conditional Content Inline macros. For example a section on the page which contains these Scroll Conditional Content legacy macro blocks, you could re-write the part using a Scroll Conditional Content Inline macro without a link and then delete the legacy macro blocks which were created during conversion. ![image-20251119-141204.png](https://migration.k15t.com/__attachments/a_7ba66e1611958f3249c3a131b958f6fef19831ea0b512013bd9f7b804ebc8d9b/image-20251119-141204.png?cb=649251c17ac52dd5a60e953494bd8b40) Scroll Conditional Content Inline macro in Scroll Content Manager ### Do I need to change my content management process somehow? You can keep creating conditionalized content as you have done so far with the help of * Scroll Conditional Content and * Scroll Conditional Content Inline macros You can edit the content in the existing macros, but you would need to edit also then unconditionalized part in the "fallback" macro. Alternatively, you can re-write the content as described in [https://k15t.jira.com/wiki/spaces/MH/pages/15360491522/Conditional+Inline+Macros+with+Elements#Can-I-convert-Scroll-Conditional-Content-legacy-macro-block-to-a-normal-macro%3F](https://migration.k15t.com/scroll-apps/migration/conditional-inline-macros-with-elements.md#Can-I-convert-Scroll-Conditional-Content-legacy-macro-block-to-a-normal-macro?) ### What is a meaning of true / false values and group id in the legacy macro block? These values hold only a technical meaning to support the conditional content functionality. GroupId is used to bundle all relevant macros together and help to map the fallback macro with them. True as a value means that this block was selected to be the fallback during the conversion process. ![image-20251118-114007.png](https://migration.k15t.com/__attachments/a_f79463bc5dc4b124eaa363c36a9499c47770675fedc3c26ae4cadc848ba7e2ab/image-20251118-114007.png?cb=96ada1229cd348e03ed28f3b76e5229f) GroupId in legacy macro block ### In which scenario I should change the legacy block macro to "fallback"? It is not recommended to change which macro block was selected to be fallback in conversion, otherwise your content might no longer work as expected. ![image-20251119-124801.png](https://migration.k15t.com/__attachments/a_42f25521711536de41a5923ecb21f1e72d9515b9388e53c9a5f2687b86f9d0e4/image-20251119-124801.png?cb=81a5c5cc06c6cdc0db919e6662b480aa) Edit screen of a Scroll conditional content legacy block Macro ### Can I delete "fallback" macros? You should not delete these fallback macros, unless you want to stop showing unconditionalized part of your content or if you are re-writing the content with the Scroll Conditional Content and Scroll Conditional Content Inline macros. ### I do not find a variant called "fallback", why? Fallback is not visible in the variant list because it is not actually a variant and the content in a fallback tagged macro is unconditionalized and should be shown to all variants for which there is no other legacy block macro with the same ID. --- version: "v4" language: "en" --- # Conversion Progress Now Always Visible in the UI - April ´26 Scroll Versions 4.8.9 brings a handy improvement to how conversion progress to Scroll Content Manager is displayed. In the past, when you started a conversion, the progress of the conversion was shown in a pop-up window. That worked fine as long as you kept the tab open and your Confluence connection stayed active. But if either of those things changed, a dropped connection, an accidentally closed tab, a browser refresh, the pop-up was gone, and so was your visibility into the conversion status. The only workaround was to check progress through the support resource API directly in the browser, which wasn't exactly convenient experience. ## What's Changed You can now check on a running conversion at any time. Simply navigate back to the **Convert to Scroll Content Manager**view and the progress bar will be right there, reflecting the current status of your conversion. ![Screenshot 2026-05-12 at 09.03.31.png](https://migration.k15t.com/__attachments/a_ba53c5618f5845bacb8acff67a67b87cbb1d031d5cd139776aaa56c6f43b4a59/Screenshot%202026-05-12%20at%2009.03.31.png?cb=40d27f81697ce454be62435bba4209ea) Conversion progress bar Especially large conversions can take a while. You shouldn't need to keep a tab open just to stay up to date on your conversion. This change gives you the freedom to navigate away and come back without losing track of what's happening. --- version: "v4" language: "en" --- # Conversion with Duplicate Page Titles This article prepares you for what happens to [*Duplicate page titles*](https://help.k15t.com/scroll-versions/4.5/?contextKey=duplicate-page-titles&version=latest&variant=default) when converting from Scroll Versions to Scroll Content Manager. ## How Duplicate Page Titles Are Converted **Scroll Documents** has been rebranded to **Scroll Content Manager**. Although the Loom video refers to the original name, all features shown in the video remain available. With Scroll Versions' *Duplicate page title* feature, you can create pages with the same page title by disconnecting the title from the page's URL. When you convert to Scroll Content Manager, these D*uplicate page titles* are converted to [*Scroll Page Titles*](https://help.k15t.com/scroll-doc/?contextKey=add-scroll-page-titles&version=latest&variant=default), but they work a bit differently to the *Duplicate page titles* in Scroll Versions. Here's what you need to know: * **Confluence needs unique titles:** Confluence requires each page within the same space to have a unique title. So, after converting to Scroll Content Manager, Confluence will add numbers to the end of some duplicate titles to keep them unique. * **Your duplicate titles are still useful!** Scroll Content Manager converts those duplicate titles into *Scroll Page Titles*, which will be used when exporting offline assets with with our Scroll Exporters or when you publish with Scroll Sites. So, while you can still use *Duplicate page titles* , as *Scroll Page Titles*, for exports and Scroll Sites content, Confluence will make the page titles unique within Confluence by adding numbers where necessary. For example, let's consider a page tree where all three child pages have the same page title (achieved through the Scroll Versions *Duplicate page title* feature) in the same space. After converting to Scroll Content Manager, the first three child pages will retain their page titles (as they were created first), while the last three will have a number added to them: | **Before conversion** | **After conversion** | |-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| | * Product A * Introduction * How to * FAQ * Product B * Introduction * How to * FAQ | * Product A * Introduction * How to * FAQ * Product B * Introduction 1 * How to 1 * FAQ 1 | The additional numbers can be manually removed after the migration, but it is also possible to address this before migrating to Scroll Content Manager. For more information, see: [Prevent Numbered Page Titles in Duplicate Page Title Conversion](https://migration.k15t.com/scroll-apps/migration/how-to-convert-a-space-with-duplicate-page-titles.md) ## Need Duplicate Page Titles in the Same Confluence Space? If you still wish to work with duplicate page titles within the same space after converting to Scroll Content Manager, you can utilize Scroll Content Manager' version prefix. This enables you to differentiate pages with similar titles by adding a prefix to the version. To learn more about this feature, we recommend reading the article: [Edit Version Prefix](https://help-cloud.k15t.com/scroll-docs?contextKey=k15t-docs-help-edit-instance-props&version=latest&variant=default) ## Want to Migrate Duplicate Page Titles Without Scroll Content Manager? Do you have spaces that only use Scroll Versions' *Duplicate page title* feature? You can migrate those spaces to Confluence Cloud *without* converting them to Scroll Content Manager. Here's how: 1. Make sure you have Scroll Versions 4.6.0 or later installed. 2. Migrate the space as a normal Confluence space using Atlassian's Migration Assistant. Your *Duplicate page titles* will be saved as *Scroll Page Titles* in Confluence Cloud. This means: * If you're publishing to Scroll Sites or exporting with Scroll Exporter apps, the *Scroll Page Titles* will be used. * You'll still see numbers added to the end of duplicate page titles within Confluence Cloud. To edit *Scroll Page Titles* after migration, install the [Scroll Exporter Extensions](https://marketplace.atlassian.com/apps/1217037/scroll-exporter-extensions?hosting=cloud&tab=overview) app. --- version: "v4" language: "en" --- # Conversion with Include Libraries To see how much the Include Libraries are used in the space, view [content reuse reports](https://help.k15t.com/scroll-versions/4.7/intro-to-content-reuse#id-(4.7)IntrotoContentReuse-ContentReuseReports). Scroll Versions and Scroll Translations provide users with the ability to reuse content from other versioned or translated spaces. However, the process of reusing content between documents will be different when you convert to Scroll Content Manager. This article outlines the changes in the concept of an Include Library that you'll experience when converting to Scroll Content Manager. If the conversion outcome described below does not meet your needs, we recommend postponing the migration and contacting our support team at [++help@k15t.com++](mailto:help@k15t.com) for assistance. ## Include Libraries in Scroll Versions and Scroll Translations In Scroll Versions or Scroll Translations, an Include Library is established by connecting an author space with a library space. This connection is based on version and/or language mapping. The content from the library space is then reused in the author space using the Scroll macro called Include+. Here's an overview of how the Include Library concept works between two versioned spaces: ![An Include Library setup with Scroll Versions and Scroll Translations](https://migration.k15t.com/__attachments/a_e0b9cfa10033cd10946899d94aff0a74c3d4a9701a8750bd3e7520cb3f3062db/scroll-versions-content-reuse.png?cb=ae7680e4f186e3fbb210be09f5618f4e) ## Include Libraries after Conversion to Scroll Content Manager When transitioning your author space to Scroll Content Manager, **we recommend sticking to the default settings** **in the conversion dialog**. This entails: * **Not selecting** "Resolve (Excerpt) Include macros in the Working version." * **Selecting** "Resolve (Excerpt) Include macros across all saved versions." ![resolve-include-macros.png](https://migration.k15t.com/__attachments/a_a6ff444c2c3caeb5f12e51265067bba88742110d7ddf2ae4c3e3974f78f02611/resolve-include-macros.png?cb=0d9878c36d13914a58676f851d2eaed8) By doing this, an _SvIncludeLibrary page and all reused pages will be copied into your new Scroll Content Manager managed space. These will be placed outside of the document. This setup enables you to continue reusing content within your Working version. Additionally, include macros in already saved versions will be resolved, rendering the content as a static part of the page. This also means that if you make any changes to the source page of the resolved includes, these changes will not be reflected. During the conversion process, (Excerpt) Include+ macros are transformed into Confluence native Include Page and Excerpt Include macros. Here's an example of how the page tree of the converted space can look like with the Include Library placed outside the Working version of your document while still reusing content through Include macros. ![An Include Library setup after conversion to Scroll Documents](https://migration.k15t.com/__attachments/a_249314deb7ff84ef66f871479dedc6f19456b6eaa6315cff274353aaa15f44af/include-library-after-migration.png?cb=b45614c0220f3d519e8d1b0e9ae0c194) ## Why Do I See a Warning on the _SVIncludeLibrary Page? After converting to Scroll Content Manager, you'll also see the following panel on the _SVIncludeLibrary page: This page contains content published from a space that is using an include library. Do not edit or move this page or its child pages. Doing so will affect your published content. This warning is added to remind you that the child pages of this page are reused by other pages in the document. If you edit or move these reused pages, it will affect how the included content is displayed within the different versions of your document. Therefore, it is important to consider the impact on the pages that reuse this content before making any changes. **Tips** To see where a page is reused, go to the Confluence page view, click **More actions** (•••) \> **Advanced details** \> **Page information**and look for "Incoming Links." --- version: "v4" language: "en" --- # Convert Welcome to the fourth and final phase of your conversion journey! In this phase, we're gearing up to convert your spaces into Scroll Content Manager managed spaces. But before starting this final phase, make sure you have followed the steps in the previous phases: * [Understand](https://migration.k15t.com/scroll-apps/migration/understand.md), * [Assess](https://migration.k15t.com/scroll-apps/migration/assess.md), * and [Prepare](https://migration.k15t.com/scroll-apps/migration/prepare.md). Here's what you'll be doing in the conversion phase: 1. **Health Check:** Give your spaces one last Scroll Health Check to make sure they're in good shape for the conversion. 2. **Conversion:** Take the leap and start converting your Scroll Versions and/or Scroll Translations managed spaces to Scroll Content Manager. ## The Goal of This Phase The goal here is to convert your relevant spaces to Scroll Content Manager. To make it happen, here's what you need to do: * **Read the articles:** Get familiar with how to convert your spaces to a Scroll Document and explore the different conversion options. * **Do the final health check:**Run a last Scroll Health Check to ensure no new blockers have surfaced. * **Convert the spaces:** Take action and start converting your spaces into Scroll Content Manager managed spaces. * **Review the result:** Make sure everything was converted as expected. This is your final checkpoint before you're all set to start working with Scroll Content Manager! ## Next Steps Before you run the health check and prepare for conversion, read the articles below: * [Convert a Space to Scroll Content Manager](https://migration.k15t.com/scroll-apps/migration/convert-a-space-to-scroll-documents.md) * [Conversion Options](https://migration.k15t.com/scroll-apps/migration/migration-options.md) --- version: "v4" language: "en" --- # Conversion with Master Spaces This article helps you decide what to do with spaces identified as "master spaces" in your migration report. ## What is a Master Space? A master space is a space that: * Contains versions, variants, duplicate page titles (permalinks), and/or languages managed by Scroll Versions and/or Scroll Translations. * May have published some of this content to other spaces ([target spaces](https://migration.k15t.com/scroll-apps/migration/convert-a-target-space.md)). ## Convert Master Spaces to Scroll Content Manager If you want to continue versioning, conditionalizing, or translating content in a master space and migrate to Cloud, you need to convert it to Scroll Content Manager. Duplicate page titles (permalinks) is not available in Scroll Content Manager. To learn more how these will be converted, see: [Conversion with Duplicate Page Titles](https://migration.k15t.com/scroll-apps/migration/conversion-with-duplicate-page-titles.md) Unsure about the conversion path? For more information, see [The Conversion Path](https://migration.k15t.com/scroll-apps/migration/the-conversion-path.md) ## Continue to Publish After Converting to Scroll Content Manager If you previously used Scroll Versions to publish within Confluence from your master space, you can continue publishing with Scroll Content Manager after converting your space. Key differences: * **Remote Publishing:** Scroll Content Manager doesn't support publishing to Confluence instances outside of your own. * **Publishing within the Same Space:** Unlike Scroll Versions, Scroll Content Manager doesn't offer the *Public View* and *Author View* feature for publishing within the same space. To publish within your authoring space, you'll need to choose a specific parent page as the publishing destination. To learn more about the differences in publishing between Scroll Versions and Scroll Content Manager, see [Publish Versions and Variants](https://migration.k15t.com/scroll-apps/migration/publish-versions-and-variants.md) ## Conclusion If your migration report shows one or more master spaces, review each one. Do you want to continue versioning, conditionalizing, or translating its content in Confluence Cloud? * **Yes:** [Convert the space to Scroll Content Manager](https://migration.k15t.com/scroll-apps/migration/the-conversion-path.md)before migrating to Cloud. * **No:** You can still migrate the space to Cloud, but first, deactivate Scroll Versions and/or Scroll Translations in that space. For more information, see: * [Deactivate Scroll Versions](https://help.k15t.com/scroll-versions/?contextKey=deactivate-scroll-versions&version=latest&variant=default) * [Deactivate Scroll Translations](https://help.k15t.com/scroll-translations/?contextKey=deactivate-scroll-translations&version=latest&variant=default) If the report also shows target spaces, see [Conversion with Target Spaces](https://migration.k15t.com/scroll-apps/migration/convert-a-target-space.md). --- version: "v4" language: "en" --- # Convert a Space to Scroll Content Manager In this article, we'll walk you through the steps to convert a space managed by Scroll Versions or Scroll Translations into a Scroll document using the Scroll Content Manager. This process consists of four stages: 1. [Control the Apps and Their Versions](https://migration.k15t.com/scroll-apps/migration/convert-a-space-to-scroll-documents.md#control-the-apps) 2. [Run the Scroll Health Check](https://migration.k15t.com/scroll-apps/migration/convert-a-space-to-scroll-documents.md#health-check) 3. [Go over the Conversion Options](https://migration.k15t.com/scroll-apps/migration/convert-a-space-to-scroll-documents.md#conversion-options) 4. [Perform the Conversion to Scroll Content Manager](https://migration.k15t.com/scroll-apps/migration/convert-a-space-to-scroll-documents.md#convert) ## 1. Control the Apps and Their Versions To kick off the conversion, you need to ensure you have the right apps and the required versions installed: * **Scroll Content Manager (previously named Scroll Documents):** At least version3.X has to be installed in order to perform a conversion. * **Scroll Versions and/or Scroll Translations:** Make sure you have the latest compatible version with your Confluence instance. If your Confluence version supports it, we recommend using the latest versions of**all apps** whenever possible. Here's how to confirm if you have the correct apps and versions: 1. Navigate to Confluence administration via the cog icon. 2. Click **Manage apps.** 3. Look for the apps in the list. If any of the required apps are missing, generate Data Center evaluation licenses for them (you can do this even if you're still on Server). ## 2. Run the Scroll Health Check Once you've confirmed all the apps and their correct versions, it's time to run one last Scroll Health Check in your spaces to ensure no new problems have surfaced that could delay your conversion: 1. Navigate to the desired space. 2. Go to **Space tools** \>**Scroll add-on** s \> **Health Checks**. 3. Click **Check**. If an error or warning appears, click **Repair** if the option is available. If there's no repair button and you see an error, try resolving it manually[following the documentation](https://help.k15t.com/scroll-versions/?contextKey=health-check&version=latest&variant=default) or [contact our support](https://k15t.jira.com/servicedesk/customer/portal/3/group/6/create/33) for guidance. If no errors or warnings appear, you're ready to proceed. ## 3. Go Over the Conversion Options Read the article about the [Conversion Options](https://migration.k15t.com/scroll-apps/migration/migration-options.md) before starting the actual conversion. ## 4. Perform the Conversion to Scroll Content Manager Ready to convert your space to a Scroll document with Scroll Content Manager? Here's a step-by-step guide: The screens displayed in the conversion dialog may vary depending on the features enabled in the original space. 1. **Start the conversion:** 1. Go to **Space tools** \> **Scroll Add-ons** \> **Convert to Scroll Content Manager**. 2. If there are any blockers, address them if possible. 3. Click **Start Conversion**. 2. **Confirm health check:** 1. Make sure you've run [the health check](https://migration.k15t.com/scroll-apps/migration/run-a-first-scroll-health-check.md) and click **Next**. 3. **Name your new space and document:** 1. Provide a name and space key for your new space. 2. Choose whether to copy space permissions. 3. Assign a title to your new document. 4. Click **Next**. 4. **Select languages (if applicable):** 1. Choose the languages you want to convert. 2. Click **Next**. 5. **Choose your Working version:** 1. Select the most recent version as your Working version. ![check mark](/__attachments/a_df3fd5a38dbc956984ffb635c888011595d3a7cc5a3deb0d6e58cfcb0d874fc7/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Tips:**The Working version is a dedicated draft version in a Scroll document. In most cases, the most recent version is the right choice here. 2. Click **Next**. 6. **Select versions to save:** 1. Decide how many versions you want to convert as saved versions. ![check mark](/__attachments/a_df3fd5a38dbc956984ffb635c888011595d3a7cc5a3deb0d6e58cfcb0d874fc7/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Tips:** Saved versions are similar to space versions in Scroll Versions. We recommend [leaving out old or outdated versions](/scroll-apps/migration/decide-what-to-keep.md) as this can help keep your new Scroll document lighter. 2. Click **Next**. 7. **Page label naming (if applicable):** 1. (Optional) Adjust the page labels for variants. 2. Click **Next**. 8. **Review conversion options:** 1. Review the [Conversion Options](https://migration.k15t.com/scroll-apps/migration/migration-options.md) and click **Next.** ![check mark](/__attachments/a_df3fd5a38dbc956984ffb635c888011595d3a7cc5a3deb0d6e58cfcb0d874fc7/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) **Tips:** We suggest sticking with the default options during conversion unless your testing indicates that different options would be more beneficial. 2. Click **Next**. 3. Review and potentially adjust other [conversion options](https://migration.k15t.com/scroll-apps/migration/migration-options.md) if needed. 9. **Start the conversion:** 1. Click **Start Conversion**. 2. Wait for the conversion to complete. 10. **Initiate the second phase of the conversion:** 1. Go to your new space. 2. Navigate to **Space tools** \> **Scroll add-ons** \> **Convert to Scroll Content Manager.** 11. **Complete remaining actions:** 1. Review the content to ensure everything is as expected. Click **Confirm**. 2. (Optional) Migrate links from other spaces to point to your new Scroll Content Manager-managed space. To migrate the links: 1. Click **Migrate**. 2. Check the box "I confirm that I read and understood the impact of this action", click **Migrate**. ⚠️ **Please note:**This action cannot be undone. 3. Click **Finalize** to complete the conversion. 12. **Adjust space permissions:** 1. Update space permissions to grant access to the necessary users. 🎉 **Congratulations** You have now converted your first space to a Scroll document before migrating to Data Center or Cloud. --- version: "v4" language: "en" --- # Conversion with Target Spaces This article helps you decide what to do with spaces identified as "target spaces" in your migration report. ## What is a Target Space? A target space is where you've published content from a [master space](https://migration.k15t.com/scroll-apps/migration/convert-a-master-space.md) (a space managed by Scroll Versions and/or Scroll Translations). The way you've set up your master space influences how its target spaces are managed. This means you'll need to handle each target space differently during migration: * If the master space only used Scroll Versions' version and/or variant feature, the target space is a normal Confluence space. * If the master space used *Duplicate page titles* (permalinks) or translations, those features will also be active in the target space, making the space still managed by Scroll Versions or Scroll Translations. ## What to Do with Target Spaces During Migration? How you handle your target space during migration depends on what's in it and how you're using it. ### Scenario 1: Target space contains only a published version or variants If you've published versions and variants to a target space, here are some key points to remember: * **Generally, you don't need to do anything.** Simply migrate the target space as a normal Confluence space. * **Consider deleting the target space if you don't need it for:** * Creating new content * Archiving **Important considerations for continued publishing** Want to keep your target space to continue publishing after converting to Scroll Content Manager? We would recommend to rethink that: * **Conflicts:** Scroll Content Manager cannot update the existing pages in your target space. Scroll Content Manager will create a new page tree in the target space, which can clash with your old content. You'd then need to delete or move those old pages. **A better way:** 1. Migrate only your master space (converted to Scroll Content Manager). 2. Create a new target space in Confluence Cloud (use the same space key if you like). 3. Publish to this new space. 4. Continue publish updates from the Scroll Content Manager managed author space. This avoids conflicts and keeps things simple. ### Scenario 2: Target space contains Duplicate page titles (Permalinks) If your target space contains *Duplicate page titles* (permalinks), here's what you need to know: * **If the space only contains** ***Duplicate page titles*** **you can migrate it as a normal Confluence space.**You do not need to convert this space to Scroll Content Manager. * **Consider deleting the target space if you don't need it for:** * Creating new content * Archiving [Remember the considerations for continued publishing mentioned earlier](#) ⬆️ * **If you use** ***Duplicate page titles*** **in your Confluence space and publish your content to Scroll Sites or export it using Scroll Exporter apps, you can partially keep those duplicate titles** .Just ensure you have at least Scroll Versions 4.6.0 installed before migrating to Cloud. **Important note about** ***Duplicate page titles*** **in Confluence Cloud** While *Scroll Page Titles* help preserve duplicate titles in Scroll Sites and Scroll Exporter exports, Confluence Cloud still has limitations. If you migrate pages with the same *Duplicate page title* , Confluence will add numbers to the end of those titles, just like when converting a space to Scroll Content Manager before migrating to Cloud. To learn more, see: [Conversion with Duplicate Page Titles](https://migration.k15t.com/scroll-apps/migration/conversion-with-duplicate-page-titles.md) ### Scenario 3: Target space contains translations If your target space contains translations, keep the following in mind: * **If you need any of Scroll Translations features:** Convert the target space to Scroll Content Manager * **Consider deleting the target space if you don't need it for:** * Creating new content * Archiving * Displaying translated content with Scroll Sites * Exporting specific languages with Scroll Exporter apps [Remember the considerations for continued publishing mentioned earlier](https://migration.k15t.com/scroll-apps/migration/convert-a-target-space.md#continued-publishing) ⬆️ ## Conclusion Here's a summary of your options for handling your target space during the migration process: * **Keep the target space if:** * You create content directly in the target space. * You use it to show translated content with Scroll Sites. * You use it to export specific languages with Scroll Exporter apps. * You need it for archiving old versions of your docs. [For instructions on how to migrate the space, refer to the sections above](#)⬆️ * **Consider deleting the target space if:** * You are converting the master space to Scroll Content Manager and migrating it to Cloud. * You're only using your target space as a publishing destination. Scroll Content Manager can't update existing content in a target space that wasn't originally published from the same document. Considernot migrating the target space and simply publishing to a new target space using the migrated master space on Confluence Cloud. * **Duplicate page titles is a limitation in Confluence:** * If you migrate a space with *Duplicate page titles* , Confluence will add numbers to the end of those titles. However, if you publish to Scroll Sites or export with Scroll Exporter apps, you can use the *Scroll Page Title*feature to keep those duplicate titles within the publishing context. Want to update your Scroll Page Titles after migrating? Install the [Scroll Exporter Extensions](https://marketplace.atlassian.com/apps/1217037/scroll-exporter-extensions?hosting=cloud&tab=overview) app. --- version: "v4" language: "en" --- # Conversion with Conditional Content Conditional content macros in Scroll Versions enable you to control the visibility of content based on specific conditions. This article explains what happens to Conditional Content macros after a conversion to Scroll Content Manager and[its extension app, Variants for Scroll Content Manager](https://migration.k15t.com/scroll-apps/migration/enhanced-variant-and-language-management-scroll-do.md). ## Transformation and Limitations When you convert to Scroll Content Manager, your Conditional Content macros are transformed into Scroll Conditional Content macros, the Scroll Content Manager counterpart. It's important to note that Scroll Content Manager and Variants for Scroll Content Manager do not support inline macros. This means that any inline Conditional Content macro you migrate, as well as any new Scroll Conditional Content macros you create, will be transformed/created as blocks. As a result, the content within each Scroll Conditional Content macro will be displayed on a new line. To learn more about the differences when managing variants and conditional content between Scroll Versions and Scroll Content Manager, see: [Manage Variants and Conditional Content](https://migration.k15t.com/scroll-apps/migration/manage-variants-and-conditional-content.md) ## If You Convert with Inline Conditional Content During the conversion process, Scroll Versions provides you with the [option to "Preserve inline Conditional content macros."](https://migration.k15t.com/scroll-apps/migration/migration-options.md) You only need to select this option if you have inline Conditional Content macros on the same line as other text content. If checked, the conversion tool will detect the paragraph around one or multiple inline conditional content macros and make the whole paragraph conditional, with different inline content in each of them. This results in equivalent output when publishing or exporting the content, the page view of the content might look less clear. Below are some examples of conditional content macros migrated with and without the option to preserve inline conditional content. **Conditional content before conversion:** ![Conditional Content macros before conversion to Scroll Documents](https://migration.k15t.com/__attachments/a_3e7acad7f5f723d7c46d376abec48bb1b907980e9175cc4fd72a7c452a7b6bd0/inline-conditional-content-macros.png?cb=49d64527922ec3d28112ad6ba93ef7cd) The following sentence contains two inline condition content macros **Conditional content after conversion:** ![Conditional Content macros after conversion to Scroll Documents](https://migration.k15t.com/__attachments/a_ad6520d7a011e2c1ded7333b914c2dab086bcb0ad3acb3ec89cdc9c4a280fa3e/inline-conditional-content-after-conversion.png?cb=6a0e39db1556ae49a2ceb717a3e6abba) Editor view after conversion without preserving inline conditional content (left) and with preserving conditional content (right) If you have multiple variants, you'll see the converted macros stacked on top of each other in the Confluence page view. However, when using Scroll Viewport, the Document Reader, or exporting with Scroll Exporters, only the content from the selected variant will be visible. --- version: "v4" language: "en" --- # Data Center Support for K15t Apps As Atlassian phases out **Data Center products** by March 2029, many customers are asking about K15t's commitment to supporting our apps in Data Center environments. We want to be as transparent as possible and provide guidance for planning your next steps. ## Will K15t Continue to Support Data Center Apps? Yes -- we have no plans to discontinue maintenance or support for our Data Center apps. Our team will continue to provide bug fixes, security updates, and technical support for all Data Center users until the official end of life for Atlassian Data Center. ## Planning Your Move to Cloud While Data Center apps will remain supported for now, we encourage customers to start planning their migration to Cloud as soon as possible. Migrations often take longer than expected, and beginning early ensures a smoother transition. For Cloud alternatives: * **Scroll Content Manager** is our next-generation solution for versioning and content management on Confluence Cloud. * For advanced needs like translations and variants, we offer **Translations for Scroll Content Manager** and **Variants for Scroll Content Manager**. We've also released **automated conversion paths** in Scroll Versions and Scroll Translations to make moving to Scroll Content Manager as smooth as possible. ## Atlassian's Support for Migration Atlassian is rolling out programs to help enterprise customers move to Cloud, including **FastShift** , which accelerates migration timelines for large organizations. [Learn more about FastShift →](https://www.atlassian.com/migration/fastshift) You can also explore Atlassian's own guidance on the [**Data Center end-of-life and cloud transition** →](https://www.atlassian.com/migration) ## Need Help or Have Questions? Our team is here to support you at every step -- whether you want to maintain your Data Center apps for now or start planning your move to Cloud. 📧 Reach out to us directly at [**help@k15t.com**](mailto:help@k15t.com) --- version: "v4" language: "en" --- # Dealing With External Links After Conversion Consider a space **S** in which two or more versions are managed using Scroll Versions. This space may contain external links to content within it, absolute links to a page in S, potentially embedded in an email or bookmarked in a browser. Suppose this space S has now been converted to Scroll Content Manager, as described here: [Scroll Content Manager Conversion](https://migration.k15t.com/scroll-apps/migration/convert.md). As a result, a new space, **SCM**, now contains all the content originally held in space S. Toward the end of this conversion process, internal links, links from other Confluence pages to content in space S, are migrated to point to the corresponding content in space SCM. However, this raises a question: what happens to the external link in your email that still points to a page in space S? That link should now point to the corresponding page in space SCM instead. What happens to the link in your email to a page in space S? This link to a page in space S *should* now point to the corresponding page in space SCM. Since links located outside of Confluence cannot be updated automatically, the only viable option is to establish your own redirect mechanism. 1. **Obtain the Page ID Mapping** Retrieve the mapping between the page IDs of source pages and their corresponding converted content (see below for details). 2. **Establish a Redirect Process** For example, if you access Confluence through a reverse proxy, you can implement the following redirect logic: 1. *Links to Page IDs* /pages/viewpage.action?pageId=0815 → /pages/viewpage.action?pageId=4711 where `0815` is the source page ID mapped to converted page ID `4711`. 2. *Tiny links* Tiny links must first be resolved to their corresponding page ID. This can be accomplished using a script such as the following: def tiny_to_page_id(tiny): return int.from_bytes(base64.b64decode(tiny.ljust(8,'A').replace('_','+').replace('-','/').encode()),byteorder='little') *Example* /x/EIFE → EIFE → 4489488 → page ID mapped from source ID 4489488. **Redirect Will Break After Cloud Migration** Following a Cloud migration, these external (absolute) links will no longer be valid. This is not only because the domain portion of the URL changes, but also because page IDs differ between Data Center and Cloud --- a page with ID *I* in Data Center will have a different page ID, *IC*, in Cloud. ## Obtaining The Page ID Mapping The mapping between source content in Scroll Versions- and/or Scroll Translations-enabled spaces and content in the converted space is stored per conversion, within the converted space itself (in this example, space SCM). ### 1. Retrieve Attachment ID The page ID mapping is stored in an attachment associated with each conversion. To retrieve this attachment's ID, call the following REST endpoint for the converted space SCM: /rest/api/space//property/sv-documents-conversion?expand=value This returns a response JSON object like: ![statusResponse.png](https://migration.k15t.com/__attachments/a_db3091fc5bd42994ea55bf6ed788b1e09b198efbf62c1ba65ef24d9471873bfd/statusResponse.png?cb=600054c6d5145ace47de045664920ecb) This response will include an attribute named `publishedContentReportAttachmentId` --- in this example, `4489467`. This is the attachment ID you will need in the next step. ### 2. Retrieve The Attachment Download Link Using the attachment ID obtained above, call the following REST endpoint to retrieve a download link for the attachment: /rest/api/content/ This returns a response like ![downloadLink.png](https://migration.k15t.com/__attachments/a_290ef3a27a982768595abe8b2bb8d837ef6db16ed6d2372814816a84b174ef64/downloadLink.png?cb=259ae59783c0d1f2b1764ba2c62aac91) The attachment can then be downloaded by appending the `_links.download` value returned in the response to your base URL, for example: /download/attachments/4489463/sv-published-content.json?version=1&modificationDate=1784883700017&api=v2 ### 3. Open And Interpret The Attachment The downloaded attachment is a JSON file with the following structure: Sample sv-published-content.json JSON { "scmSpaceKey": "CVTS", "docSpaceKey": "CCON", "pageMappings": [ { "version": { "name": "2.0", "isWorkingVersion": true, "workingVersion": true }, "language": { "code": "de", "displayName": "German", "isOriginalLanguage": true, "originalLanguage": true }, "scmPageIdToDocPageIdMapping": { "4489221": 4489386, "4489222": 4489386, "4489280": 4489392, "4489218": 4489383, "4489250": 4489383, "4489310": 4489389, "4489311": 4489389, "4489279": 4489392 } }, { "version": { "name": "2.0", "isWorkingVersion": false, "workingVersion": false }, "language": { "code": "de", "displayName": "German", "isOriginalLanguage": true, "originalLanguage": true }, "scmPageIdToDocPageIdMapping": { "4489221": 4489403, "4489222": 4489403, "4489280": 4489409, "4489218": 4489400, "4489250": 4489400, "4489310": 4489406, "4489311": 4489406, "4489279": 4489409 } }, { "version": { "name": "2.0", "isWorkingVersion": false, "workingVersion": false }, "language": { "code": "en", "displayName": "English", "isOriginalLanguage": false, "originalLanguage": false }, "scmPageIdToDocPageIdMapping": { "4489221": 4489419, "4489222": 4489419, "4489280": 4489425, "4489218": 4489416, "4489250": 4489416, "4489310": 4489422, "4489311": 4489422, "4489279": 4489425 } }, { "version": { "name": "1.0", "isWorkingVersion": false, "workingVersion": false }, "language": { "code": "de", "displayName": "German", "isOriginalLanguage": true, "originalLanguage": true }, "scmPageIdToDocPageIdMapping": { "4489221": 4489435, "4489222": 4489435, "4489280": 4489441, "4489218": 4489432, "4489250": 4489432, "4489310": 4489438, "4489311": 4489438, "4489279": 4489441 } }, { "version": { "name": "1.0", "isWorkingVersion": false, "workingVersion": false }, "language": { "code": "en", "displayName": "English", "isOriginalLanguage": false, "originalLanguage": false }, "scmPageIdToDocPageIdMapping": { "4489221": 4489451, "4489222": 4489451, "4489280": 4489457, "4489218": 4489448, "4489250": 4489448, "4489310": 4489454, "4489311": 4489454, "4489279": 4489457 } } ], "blogPostMapping": { "scmBlogPostIdToDocBlogPostIdMapping": { } } } Because Scroll Content Manager maintains a separate page for each version --- and, where applicable, for each language within each version --- you will find multiple page ID mappings stored within the `scmPageIdToDocPageIdMapping` attribute for each version/language combination. The "left-hand" page ID represents the source page ID --- that is, the ID of the page for the given version within the Scroll Versions- and/or Scroll Translations-enabled space (space S in the example above): ![pageIdMappings.png](https://migration.k15t.com/__attachments/a_23d6a9c4fe31cb14b90676212fef939bd724cf12b80037a15971bd8f9249784c/pageIdMappings.png?cb=44248e48ef2ada54647596524a285150) **A 1:n Mapping Should Be Expected - Default Must Be Defined** In Scroll Versions- and/or Scroll Translations-enabled spaces, not every version necessarily has its own distinct page for a given piece of content: multiple versions may reference the same page if that content was not updated across those versions. As a result, a single source page ID may map to multiple different converted page IDs within this mapping file. When multiple languages are in use, this 1:n relationship applies to every page, since Scroll Versions- and/or Scroll Translations-enabled spaces manage all languages within a single page --- unlike Scroll Content Manager, which manages each language on a separate page. Consequently, you will need to determine a default version (and, where applicable, a default language) to use when resolving a source page ID that maps to multiple converted page IDs. --- version: "v4" language: "en" --- # Decide What to Keep – Streamlining Your Content Are you gearing up to convert from Scroll Versions to Scroll Content Manager? It's a significant step forward, and we're here to guide you through the process. In this article, we'll outline the important task of preparing your existing content. Let's make sure you migrate only what's essential, leaving behind the all the clutter and outdated content. ## Check the Spaces: A Thorough Analysis Much like tidying up the attic and basement before shifting homes, take time to assess your content and determine what truly needs to make the move. Before diving into the migration process, be sure to run the [Migration Report](https://migration.k15t.com/scroll-apps/migration/run-the-migration-report.md). This report helps you identify the specific features of Scroll Versions or Scroll Translations that are currently active within your spaces. It's the equivalent of surveying your new house before deciding where to place your belongings. ### Cleaning up personal spaces and unclear setups After running the Migration Report, head to the [best practices page](https://migration.k15t.com/scroll-apps/migration/effective-best-practices-using-the-space-migration.md) and kickstart your content preparation by cleaning up archived spaces, personal spaces and spaces with unclear setups. These areas are often repositories of content that may not be relevant to the conversion. **Keep the Overview** As you tidy up and go through your existing spaces, [create a Confluence page](https://migration.k15t.com/scroll-apps/migration/effective-best-practices-using-the-space-migration.md#Keep-the-overview) to keep track of the spaces and how relevant they are to the migration. ### Deciding what to keep: Ask these questions After you've gone through the obvious spaces and have decided what to do with those, it's time to look more closely into the spaces that you consider being relevant for the migration. **Did you know?** Keeping your Confluence page tree under 50,000 pages is recommended for a smoother navigation experience. For more tips and best practices on maintaining a page tree and optimizing your Confluence experience, check out this [Atlassian Community article](https://community.atlassian.com/t5/Confluence-Cloud-articles/Best-practices-for-a-great-page-tree-experience/ba-p/2486271). To make an informed decision about what to keep, ask yourself the following four questions. Note that the last two apply only if you've used variant management in Scroll Versions or managed multiple languages with Scroll Translations. #### 1. Are all my spaces still relevant? After excluding personal spaces and those with unclear setups, take a closer look at the remaining spaces and try to better understand the relevancy of a space and its content: * **Space Names:** Check your space names to identify test or sandbox spaces that might not require migration. Oftentimes those spaces can be easily identified by their space names or space keys. When in doubt, clarify with the specific space owner. * **Relevancy and Importance:** If your company has been using Scroll Versions or Translations for an extended period, you may find documentation spaces for outdated products. Exclude these from the migration to streamline your content. #### 2. Are all my versions still relevant? Over time, spaces accumulate numerous versions, many of which may no longer be relevant to your readers. These versions may even pertain to products no longer supported or used. Remember, the less you migrate, the less outdated or unnecessary content you'll have to carry over to Scroll Content Manager and your fresh Confluence Cloud or Data Center instance. ##### 2.1 Spaces with one version One version means that the content in the version is the same as the original content. In spaces where you have only one version, you have two routes to proceed: 1. [Deactivate Scroll Versions](https://help.k15t.com/scroll-versions/4.7/deactivate-scroll-versions#id-(4.7)DeactivateScrollVersions-DeactivateScrollVersionswithoneversion) in the space, if there are no plans to version the space 2. Convert the space to Scroll Content Manager if you want to keep versioning the space or want to publish it #### 3. Are all my variants still relevant? If you've made use of Variant Management in Scroll Versions, it's worth evaluating the variant setup in your spaces. Consider which variants are still essential to your current documentation needs and identify those that can be left behind. #### 4. Are all my languages still relevant? For users of Scroll Translations, it's wise to question the relevance of all the languages you've employed. As your content evolves, so do your language requirements. You can use the [Translations Report](https://help.k15t.com/scroll-translations/4.5/translations-report)in Scroll Translations to filter for translated pages per language and identify languages with minimal translated content ### The benefits of a streamlined migration By going through these questions, you pave the way for a seamless transition to Scroll Content Manager. The effort you invest in content preparation will pay off in several ways: * **Improved clarity:** Your new system will be free from clutter and outdated content, making it easier for users to find what they need. * **Efficient management:** With only essential content in place, managing this content becomes more straightforward and efficient. * **Enhanced user experience:** Readers will appreciate the relevancy and accuracy of your documentation, improving their overall experience. Remember, your goal is to make this transition as smooth as possible for both your team and your end-users. Taking the time to prepare your content, versions, variants, and languages now will save you time and effort in the long run. ## Conclusion Converting from Scroll Versions to Scroll Content Manager is an exciting step forward. By following these guidelines and carefully evaluating your existing content, you'll ensure a seamless transition that leaves you with a lean and effective documentation system. --- version: "v4" language: "en" --- # Effective Best Practices using the Space Migration Report Migrating content is like moving houses -- an opportunity to declutter and organize your digital space. Before moving all your existing content to a new Cloud or Data Center environment, we recommend taking the opportunity to bid farewell to outdated or unnecessary information. In this article, you'll learn some best practices on how to deal with certain space setups that have been managed with Scroll Versions and / or Scroll Translations. While these best practices have proven effective for many, remember that each Confluence setup is unique. Tailor these tips to your needs for a seamless migration experience. ## Check the Spaces: A Thorough Analysis Much like tidying up the attic and basement before shifting homes, take time to assess your content and determine what truly needs to make the move. Before diving into the migration process, be sure to run the [Migration Report](https://migration.k15t.com/scroll-apps/migration/run-the-migration-report.md). This report helps you identify the specific features of Scroll Versions or Scroll Translations that are currently active within your spaces. It's the equivalent of surveying your new house before deciding where to place your belongings. In the following sections we'll dive deeper into setups that we have seen in previous migration projects and how to deal with those setups and spaces best. You'll learn how to make your content ready for your move to the Cloud (or Data Center). ### Archiving: the informed choice Review all archived spaces and make well-informed decisions about whether to include them in the migration. When a space is archived, it often indicates that the content hasn't been relevant for a period, suggesting it may not hold future necessity. **🌟 Best practice:**Identify the space owners and verify the relevance of their archived spaces or whether they fall outside the scope of migration. ### Personal spaces matter Give personal spaces special attention, particularly when not all members of your organization have space admin permissions. It's a common occurrence for Scroll Versions or Translations to be activated in personal spaces for app testing and experimentation. But more often than not, these apps are not put to productive use in personal spaces. **🌟 Best practice:** Check with the space owners and ask if the apps are genuinely being used or if it was merely for testing purposes. The app(s) can be deactivated if deemed unnecessary. ### Unveiling unclear setups Having examined numerous migration reports from customers over the past few months, we've identified several instances where the rationale behind the configuration of Scroll apps remains unclear. Let's dig deeper into these configurations: #### Master Spaces with a single version The main benefit of Scroll Versions is that it enables you to manage multiple versions of your content within a single space. Upon reviewing customers' migration reports, we occasionally encountered Master Space configurations featuring only a single version. **🌟 Best practice:** Identify the space owner and clarify the reason behind having just a single version. This will enable you to make an informed decision on whether to convert the space to Scroll Content Manager or to deactivate Scroll Versions. #### Master Spaces with a single (1) variant Another advantage of Scroll Versions is its ability to customize your content for various scenarios or audiences through its variant management functionality. Although this feature is most applicable when dealing with multiple scenarios or audiences, we have encountered Master Spaces containing only a single variant. **🌟 Best practice:** Identify the space owner and clarify the reason behind configuring a single variant. Determine whether the variant management functionality remains necessary. If not, consider deactivating Scroll Versions (or the variant management functionality) for that space. #### Master Spaces with zero (0) variants In Scroll Versions, variants are defined through attributes and attribute values. In certain migration reports, we observed instances where spaces had variant management activated, yet no variants were configured. In some cases, variant management had been utilized in the past, but never properly deactivated. **🌟 Best practice:** Identify the space owner and clarify the reason behind the missing variants. Determine whether the variant management functionality remains necessary. If not, Scroll Versions (or the variant management functionality) can be deactivated in the space. #### Master spaces with no further details Scroll Versions provides additional features that are set per space and can be used independently from versioning or variant management. In some scenarios, it can happen that master spaces show up in the list, but there are no further details on those spaces (i.e. all details have the info "-"). In that case the space has either the SEO feature or the duplicate page title feature activated, but they are not used actively in the space. **🌟 Best practice:** Deactivate the corresponding feature in the Scroll Settings and migrate the space. #### Master Spaces with a Single Language Scroll Translations allows you to maintain multiple languages in one space and makes most sense when you want to manage content in multiple languages. Still we encountered setups where Scroll Translations is activated, but just a single language was defined. **🌟 Best practice:** Identify the space owner and clarify why they have activated Scroll Translations in their space. Even if they have intentions to eventually provide content in multiple languages, it might be more logical to deactivate Scroll Translations prior to migration. Since the content is currently accessible only in one language, no content will be lost upon deactivation. ## Tips and Tricks: Enhancing Your Migration ### General Tips * As the Space Migration Report only presents spaces that utilize any of the Scroll Versions and Scroll Translations features, you should review all your spaces before starting a migration to determine their ongoing relevance. * We advise having a look at the Migration Report and your space configurations even if a migration to Cloud or Data Center is not currently in your plans. Doing so helps streamline the number of spaces and ensures that your environment remains organized. ### Migration Report Tips To identify spaces with unclear setups, use the sorting function of the Migration Report and sort in ascending order (e.g. by the number of variants). Ensure that you exclusively assess the setup for Master spaces. Identifying personal spaces can be easily achieved using the space key column, given that the space key of all personal spaces starts with "\~". ### Keep the overview Depending on your internal processes and the scale (as well as age) of your Confluence system, identifying space owners and staying updated on space migration statuses could pose challenges. We therefore recommend restricting the activation of [Scroll Versions and Translations by space](https://help.k15t.com/scroll-versions/4.5/restrict-scroll-versions-activation-by-space). This step prevents the creation of new spaces while you manage the existing list. Furthermore, the results can be effortlessly preserved on a Confluence page using the following copy-paste method: 1. Mark the results of the migration report. 2. Copy the content. 3. Create a new Confluence page and paste the content. The outcome will be presented as a standard Confluence table, allowing for easy addition of new columns, such as @-mentioning the relevant space owner or tracking space statuses (e.g. needs clarification \| Delete space \| Deactivate Scroll \| Convert to DOCuments ). ## Summary These best practices have proven valuable to many, offering insights into optimizing your migration process. We hope you'll adapt them to your unique circumstances and goals. A well-structured migration can establish the groundwork for a more efficient content management journey ahead. 📦🚀 Feel free to share any additional best practices you might have. We're always eager to hear from you. --- version: "v4" language: "en" --- # Enhanced Variant and Language Management: Scroll Content Manager and its Extension Apps This page explains how Scroll Content Managersupports variant and language management, what's included out of the box, and when to consider using the extension apps for more advanced need Variant Management is a core feature in Scroll Versions, while language management is the core feature of Scroll Translations. If you have not used the variant management functionality in Scroll Versions and/or have never had Scroll Translations installed on your system, you can skip this section. ## Variant Management In content management, **variant management** enables you to tailor content for different audiences or use cases. If you're converting from Scroll Versions, it's important to understand how this works in Scroll Content Manager. ### Basic variant support (built-in) Scroll Content Manager includes a basic variant functionality using Confluence page labels to mark content for specific variants. With this built-in setup, you can: * Create **up to 2 variants** per document * Manually assign labels to control variant content * Define **simple variant rules** ### Advanced variant support To manage more advanced variant setups, install the extension app: [Variants for Scroll Content Manager](https://marketplace.atlassian.com/apps/1226295/variants-for-scroll-documents?hosting=cloud&tab=overview) With the extension, you can: * Create an **unlimited number of variants** per document * Use **bulk label editing** to speed up management of variants * Set up **complex, nested variant rules** ## Language Management If you've previously used Scroll Translations, Scroll Content Manageralso provides language support to maintain multilingual content. ### Basic language support (built-in) Scroll Content Manager includes core multilingual features: * Manage **up to 2 languages** per document * Perform **manual translation** directly in Confluence ### Advanced language support To unlock full language management, install the extension app: [Translations for Scroll Content Manager](https://marketplace.atlassian.com/apps/1227238/translations-for-scroll-documents?hosting=cloud&tab=overview) With the extension, you can: * Manage an **unlimited number of languages** * Facilitate both **manual translation and external XLIFF translation** to integrate external Translation Management Systems --- version: "v4" language: "en" --- # External Translations: Scroll Translations vs Scroll Content Manager This article explains how the external translation workflow differs between Scroll Translations and Scroll Content Manager (with the Translations for Scroll Content Manager extension). ## External Translation with Scroll Translations For external translation using Scroll Translations, the workflow generally looks like this: 1. Page content is authored in the default language. 2. A space admin exports the content to XLIFF format for translation. 3. The files are translated externally. 4. The space admin imports the translations, marking the pages as translated. 5. Users consume the translated content by switching languages in the language picker. This process will change slightly when moving to Scroll Content Manager, which also introduces versioning as a concept. ## External Translations with Scroll Content Manager In Scroll Content Manager, external translation still happens via XLIFF, but the process may incorporate versioning. This means you manage translations per version of your documentation: * **Working version**: The continuously evolving draft of your documentation. Ideally, this is where you add all new or updated content that hasn't been released yet. * **Saved versions** : Once the *Working version* is reviewed and approved, it can be saved as a new version. The saved version retains the content in the authoring language, enabling you to translate it into secondary languages. * **Language page trees**: Each language has its own set of pages under a version, enabling you to make independent changes to each version and translation. ### What if I don't want to version my content? While the recommended workflow in Scroll Content Manager is to: * Maintain the*Working version* in your defined authoring language, * save a version when content is ready, and * add or reuse translations in the saved version, you're not required to follow this process if versioning isn't relevant to your use case. For example, if you're managing a multilingual intranet or other continuously updated content without the need for version history, you can add translations directly to the *Working version* and choose not to save any versions. ## External Translation Workflows in Scroll Content Manager Scroll Content Manager supports two main external translation workflows depending on whether you're working with multiple versions or only the *Working version*. ### External translation with many versions When translating externally with several versions, the workflow is as follows: 1. Add new content to the *Working version*, which uses the defined authoring language. 2. Review the content in the *Working version* before saving the version. 3. Save the *Working version* once it's ready, which creates a new version containing the defined authoring language. 4. Create an XLIFF export and send it to a translator. 5. Import the translated files back to Confluence which will mark the pages as translated. 6. The process starts over. If you have translated previous versions, you'll also have the option to [reuse translated content](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-reuse-translations&version=latest&variant=default). ### External translation of the Working version When translating only the *Working version* externally, the workflow is as follows: 1. Add new content to the *Working version* in the specified authoring language. 2. Review the content in the authoring language. 3. If not added already, add the translations manually to the *Working version*. 4. Generate an XLIFF export and send it to a translator. 5. The process starts over when you add new content to the authoring language and you [update your existing translations](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-update-translation&version=latest&variant=default). **Note** Adding new pages should be done exclusively in the authoring language of your content, rather than in the translated page trees. When using the [synchronization feature](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-update-translation&version=latest&variant=default)during the creation of your next XLIFF file, any newly added pages within the translated page tree structure will be automatically removed. --- version: "v4" language: "en" --- # Fulfill the Conversion Requirements In this article, we will provide an overview of the different conversion requirements that should be met before converting to Scroll Content Manager. Some of these requirements may act as blockers, preventing the conversion, while others serve as warnings, highlighting changes or limitations you may encounter during the conversion process. Understanding these prerequisites is crucial for a seamless transition to Scroll Content Manager. In addition to resolving blockers, we recommend trying to resolve as many warnings as possible before converting. ## Conversion Requirements for Scroll Content Manager In the tables below you'll find an overview of the warnings and blockers you may encounter when converting to Scroll Content Manager. ### Blockers 🛑 | **Requirement** | **Description** | |--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| | Scroll Content Manager (previously name Scroll Documents) 3.0 or higher must be installed and enabled. | Ensure that your Confluence instance has the required version of Scroll Content Manager installed and activated for the conversion. | ### Warnings ⚠️ |--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Requirement** | **Description** | | Includes between versioned documents not supported. | This space's Include Library cannot be converted into a separate document. If you proceed, the included pages will be imported into the document. For more information, see: [Conversion with Include Libraries](https://migration.k15t.com/scroll-apps/migration/conversion-with-include-libraries.md) | | Workflow states currently assigned to pages will **not** be available after the conversion. | Workflow states assigned to pages using Scroll Versions' built-in workflow won't transfer during conversion. For more see: [Workflow Statuses After Conversion](https://migration.k15t.com/scroll-apps/migration/workflow-statuses-after-conversion.md) | | Only the Comala Document Management status of the latest page revision are copied during conversion. Historical workflow data is **not** copied. | For audit purposes, page statuses from Comala Document Management are copied over to the newly converted space. For more see: [Workflow Statuses After Conversion](https://migration.k15t.com/scroll-apps/migration/workflow-statuses-after-conversion.md) | | Duplicate page titles within versions not supported. | Scroll Content Manager doesn't support duplicate page titles within versions. If a conflict is detected, a number will be added to the end of the page name, e.g. "Introduction 1". For more information, read: [Conversion with Duplicate Page Titles](https://migration.k15t.com/scroll-apps/migration/conversion-with-duplicate-page-titles.md) | | Search engine optimization (SEO) won't be available. | Post-conversion, SEO settings will not be available. Please consider alternative approaches for optimizing your content. | | Translations Ignore macros will be replaced with content. | Macros related to translation management will be replaced by Scroll Content Manager's own translation macros: Scroll Non-Translatable | ## Conclusion Before converting to Scroll Content Manager, ensure that the mandatory requirements are met to prevent conversion blockers. Additionally, take note of the warnings to understand the changes and limitations that may occur during the conversion process. --- version: "v4" language: "en" --- # GDPR Compliance and Data Security In this FAQ, we address questions related to GDPR compliance and data security for our apps. Below, you'll find answers to common questions about data security, GDPR compliance, and our plans for Data Residency. ## Where Can I Find Information about Data Security and GDPR Compliance? You can find detailed information in our [Data Security Statement](https://www.k15t.com/legal/data-security-statement) and [Data Processing Addendum](https://www.k15t.com/legal/data-processing-addendum). These documents contain valuable insights into how we handle data security and comply with GDPR. ## Are There Any Plans Regarding Data Residency? We are currently in discussions with Atlassian regarding Data Residency. As these plans become more concrete, we will provide further updates and information. If you have questions or concerns in the meantime, please feel free to reach out to our support team at [++help@k15t.com++](mailto:help@k15t.com). --- version: "v4" language: "en" --- # Prevent Numbered Page Titles in Duplicate Page Title Conversion Scroll Versions offers the possibility to have multiple pages with the same page title within the same space using the concept of a permalink (see[*Duplicate Page Titles*](https://help.k15t.com/scroll-versions/4.5/?contextKey=duplicate-page-titles&version=latest&variant=default)for more details). Spaces can have this feature activated in two ways: * Intentionally as an individual setting via Scroll Versions' *Settings*. * Automatically when a space has been published from a [master space](https://migration.k15t.com/scroll-apps/migration/convert-a-master-space.md) that had the feature activated. As Scroll Content Manager does not support duplicate page titles in the same way as Scroll Versions, please read this page carefully to understand how to deal with pages that have *Duplicate page titles*. You can find out which spaces use *Duplicate page titles* by running the reporting tool described here:[](https://help-cloud.k15t.com/scroll-versions/4.5/migration-report)[Run the Migration Report](https://migration.k15t.com/scroll-apps/migration/run-the-migration-report.md) ## Duplicate Page Titles in Scroll Content Manager In Scroll Content Manager, page names are given a prefix of their version name to avoid conflicts between different versions of the same page. If there is a conflict within a version, the conversion process will make the following additions: * A number will be appended to the page title, such as "Introduction 1". * The duplicate page title will also be added as a [*Scroll Page Title*](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-help-scroll-page-title&version=latest&variant=default) to the page, but it can only be seen when viewing the page in Scroll Sites, or when exporting it using one of the Scroll Exporter apps. **If you want to avoid the numbers being added to pages with duplicate page titles** **in your space, continue reading this article.** ## Solution If you want to ensure that numbered titles are not visible in Confluence, you'll need to manually rename your pages after converting them to Scroll Content Manager on your On premise system or before migrating them to the Cloud. To clarify: * **For master spaces with** ***Duplicate page titles*** **activated:** You need to manually rename your pages after converting them to Scroll Content Manager on your On premise system. * **For spaces where only** ***Duplicate page titles*** **are activated:**You need to manually rename the pages before migrating the space with the Confluence Cloud Migration Assistant. Scroll Content Manager' conversion tool will still display an issue stating that *Scroll Content Manager doesn't support duplicate page titles within versions.* -- if you have renamed all pages, you can ignore that message. Again, if you're fine with the numbers in Confluence titles but wish to avoid them in Scroll Viewport of exports using Scroll Exporters, there's no need for any specific actions before or after conversion. The new *Scroll Page Titles* will be displayed in Scroll Viewport and Scroll exports, so you won't see those numbers. --- version: "v4" language: "en" --- # How to Read the Migration Report In this article, you'll learn more about how to interpret the results of the migration report and we will help clarify how well Scroll Content Manager supports the features you are currently using. ## How to Read the Report ![Scroll-Migration-Space-Analysis.png](https://migration.k15t.com/__attachments/a_5e800f62b73eb2fda60aefcc3ad10b982444782c748ccd9587df8b425ae10ee1/Scroll-Migration-Space-Analysis.png?cb=5132e62ea7266db2f0af38cb5b2b6db2) In the table below you'll find an overview of the entries which will appear in your report. Learn what each entry means, and if you're required to take any action when given a specific value. This table will help you understand what actions will be required to take before you can switch to Scroll Content Manager. For help in understanding the more detailed JSON format of the report, refer to the article: [How to Read the Migration Report in JSON Format](https://migration.k15t.com/scroll-apps/migration/how-to-read-the-migration-report-in-json-format.md) | **Report entry** | **This entry tells you...** | **Required actions** | **Additional recommendations** | |-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `Space Name ` | The name of the space. | No action required | - | | `Space Key` | The [space key](https://support.atlassian.com/confluence-cloud/docs/choose-a-space-key/) of the space. | No action required | - | | `Pages` | How many pages that exist in this space. | If your space has a lot of pages, take this as a chance to clean up the space by removing outdated or redundant content. | - | | `Top Level Pages ` | How many top-level pages this space has. In other words, how many pages that are on the highest level in the space. | If the value is greater than one, this means you have more than one top-level page in the space. Follow instructions from [preparing multiple top-level pages](https://migration.k15t.com/scroll-apps/migration/preparing-multiple-top-level-pages.md) | | | `Blog Posts` | How many blog posts have been created in this space. | No action required | **To keep in mind:** When converting spaces, blog posts are copied to the new space, but keep in mind: * Only the latest revision is copied. * Original creator and creation date are retained. * Last modification date is set to the conversion date. * The last modifier is set to the user who initiated the conversion. | | `Scroll Space Type ` | If the value shows: * `Master` this means this space is used to publish content into other spaces. * `Master(archive)` this means the space has been[archived](https://support.atlassian.com/confluence-cloud/docs/archive-a-space/). * `Target` this means a master space was published into this space. This target space can contain duplicate page titles or languages. | If the space is a: * `Master` space we recommend that you consider converting this space to Scroll Content Manager. To learn more, check out [Conversion with Master Spaces](https://migration.k15t.com/scroll-apps/migration/convert-a-master-space.md). * `Master(archive)` space, we recommend you double check if you want to keep the space and convert it to Scroll Content Manager. * `Target` space, think about whether you really need it. To help you make an informed decision, we recommend reading [Conversion with Target Spaces.](https://migration.k15t.com/scroll-apps/migration/convert-a-target-space.md) | We recommend to take the conversions as a chance to clean up old spaces and rather not convert archived spaces. | | `Scroll Publishing Methods` | If the value shows: * `-` this means this space has never published any content using Scroll Versions. * `to same` this means this space has been published within the same space. * `to new ` this means this space has been published to a new space. * `to existing` this means this space has been published to an existing space. * `to remote` this means the space has been published to a remote Confluence system. | With Scroll Content Manager you can publish content to a specific target space, or a parent page within your authoring space. However remote publishing to other Confluence systems is **not** available in Scroll Content Manager. This is also **not**something we are planning to implement. As an alternative solution to remote publishing we recommend that you [publish your document as an online help center](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) with [Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview). | For more information about publishing to Confluence with Scroll Content Manager, see: [Publish Versions and Variants](https://migration.k15t.com/scroll-apps/migration/publish-versions-and-variants.md) | | `Versions` | How many versions the space has. | Decide which versions are necessary to convert. **Note** In Scroll Content Manager, the number of pages in the space will be multiplied by the number of versions and languages you have in the space. In short, if you have a lot of pages, versions, and / or languages, this will affect your space size. | We suggest trying to convert as few versions as possible, and view the conversion as a good opportunity to get rid of redundant versions. | | `Branches ` | If the version tree has several branches, this value tells you how many branches. | No action required | **To keep in mind** In Scroll Content Manager it's**not** possible to create branches. Your existing version branches will be converted into a linear version tree within Scroll Content Manager. | | `Multiple Root Versions` | If the version tree has several root versions, this value tells you how many root versions the version tree has. | Multiple root versions is a legacy feature in an older version of Scroll Versions. If you find you have multiple root versions, reach out to: [help@k15t.com](mailto:help@k15t.com) | - | | `Variants` | If the space has variants, this value tells you how many variants the space has defined. | Variant management in Scroll Content Manager works with page labels. Those labels can be defined during conversion and are are automatically assigned. To learn more, read: [Manage Variants and Conditional Content](https://migration.k15t.com/scroll-apps/migration/manage-variants-and-conditional-content.md) | - | | `Attributes ` | If the space has variants, this value tells you how many attributes the space has defined. | Variant management in Scroll Content Manager works with page labels. Those labels can be defined during conversion and are are automatically assigned. To learn more, read: [Manage Variants and Conditional Content](https://migration.k15t.com/scroll-apps/migration/manage-variants-and-conditional-content.md) | - | | `Attribute Values` | If the space has variants, this value tells you how many attribute values the space has defined. | Variant management in Scroll Content Manager works with page labels. Those labels can be defined during conversion and are are automatically assigned. To learn more, read: [Manage Variants and Conditional Content](https://migration.k15t.com/scroll-apps/migration/manage-variants-and-conditional-content.md) | - | | `Languages` | How many languages are in the space. | Decide which languages are necessary to convert. **Note** In Scroll Content Manager, the number of pages in the space will be multiplied by the number of versions and languages you have in the space. In short, if you have a lot of pages, versions, and / or languages this will affect space size. | We suggest trying to convert as few languages as possible, and view the conversion as a good opportunity to get rid of redundant content. | | `Workflow` | If the value shows: * `Simple ` this means you are using the Scroll Versions[inbuilt workflow](https://help-cloud.k15t.com/scroll-versions/?contextKey=workflows-intro&version=latest&variant=default) in this space. * `Comala `this means the space uses Scroll Versions and [Comala Document Management](https://marketplace.atlassian.com/apps/142/comala-document-management?hosting=cloud&tab=overview) to manage workflows. | Scroll Content Manager has its own built-in workflow feature, but it does **not**yet integrate with Comala Document Management. We recommend reading: * [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) * [Workflow Statuses After Conversion](https://migration.k15t.com/scroll-apps/migration/workflow-statuses-after-conversion.md) It's currently not possible to convert a Scroll Versions workflow into a Scroll Content Manager workflow during the conversion process. | We will be looking into the possibility of supporting an integration with Comala in the future. If you're interested, follow the progress here: [DOCS-36](https://k15t.jira.com/browse/DOCS-36) | | `Include Library` | The[Include Library](https://help-cloud.k15t.com/scroll-versions/?contextKey=content-reuse&version=latest&variant=default) feature is in use in this space. | Continue to the report entries `Included by` and `Includes` to confirm if content from this space is included in another space, alternatively if it includes content from other spaces. | - | | `Included by ` | If the value shows `Yes` , this means this space is an [Include Library](https://help-cloud.k15t.com/scroll-versions/?contextKey=content-reuse&version=latest&variant=default). The content from this space is included in other spaces / documentation spaces. | The [Include Library feature](https://help-cloud.k15t.com/scroll-versions/?contextKey=content-reuse&version=latest&variant=default) is currently not fully supported in Scroll Content Manager. As it works currently, the included content will instead be converted into the new Scroll Content Manager managed space: [Conversion with Include Libraries](https://migration.k15t.com/scroll-apps/migration/conversion-with-include-libraries.md) The source pages of the included content will be copied and added to the top-level above the home page. | If the outcome described does not fulfill your requirements, we recommend you wait to convert and reach out to our support via: [help@k15t.com](mailto:help@k15t.com) | | `Including` | If the value shows `Yes` , this means this is a documentation space which reuses content from other spaces via an [Include Library](https://help-cloud.k15t.com/scroll-versions/?contextKey=content-reuse&version=latest&variant=default). | The [Include Library feature](https://help-cloud.k15t.com/scroll-versions/?contextKey=content-reuse&version=latest&variant=default) is currently not fully supported in Scroll Content Manager. As it works currently, the included content will instead be converted into the new Scroll Content Manager managed space: [Conversion with Include Libraries](https://migration.k15t.com/scroll-apps/migration/conversion-with-include-libraries.md) The source pages of the included content will be copied and added to the top-level above the home page. | If the outcome described does not fulfill your requirements, we recommend you wait to convert and reach out to our support via: [help@k15t.com](mailto:help@k15t.com) | | `Incoming Links` | This value assesses the amount of incoming links from other spaces that point to pages in this space. | If your Scroll Versions or Scroll Translations-managed space has incoming links from other spaces in your Confluence system, you can choose to rewrite those links so they point to the newly converted Scroll Content Manager space. To learn more, see: [Migration of Incoming Links](https://migration.k15t.com/scroll-apps/migration/migration-of-incoming-links.md) Any page that had its link rewritten during this action will be listed in the Confluence logs with its page ID for reference. | - | | `Conditional Content Macros Issues` | If the value is `1` or higher, it means there are one or more Conditional Content (Inline) macros in the space that contain content or formatting not supported by the corresponding Scroll Conditional Content Inlinemacro in Scroll Content Manager. This may impact how the content is converted. | For any space reported with a value of `1`or higher, navigate to the affected space and[run a Scroll Health Check](https://migration.k15t.com/scroll-apps/migration/run-a-first-scroll-health-check.md). This will identify the pages that contain unsupported inline Conditional Content macros. Once identified, you can decide how to handle the affected content. To learn more about your options and what this means for your conversion, see: [Conversion with Conditional Content](https://migration.k15t.com/scroll-apps/migration/convert-with-conditional-content.md) | - | To learn how to generate the report, refer to: [The Migration Report](https://migration.k15t.com/scroll-apps/migration/run-the-migration-report.md) --- version: "v4" language: "en" --- # How to Keep the Old Space Key after Converting to Scroll Documents Migrating a versioned space to the Cloud is a [two-step process](https://help-cloud.k15t.com/scroll-versions/4.5/migration-path): 1. Convert the space to a Scroll Content Manager-managed space 2. Migrate that space to the Cloud As part of the conversion in step 1, the space key will change. This article provides step-by-step instructions on how to convert a versioned or translated space to Scroll Content Manager while ensuring that the new space retains its old space key. ## Before You Start Before initiating the migration process, please ensure that you have completed the following prerequisites: * Generate a migration report and prepare the space for migration. For detailed information, refer to the article: [Run the Migration Report](https://migration.k15t.com/scroll-apps/migration/run-the-migration-report.md) * Perform at least one test migration and familiarize yourself with the migration path. For more information, see: [The Conversion Path](https://migration.k15t.com/scroll-apps/migration/the-conversion-path.md) ## Migrate with Your Old Space Key To preserve the old space key after migrating to Confluence Cloud, follow the steps outlined below: 1. Convert your Scroll Versions or Scroll Translations managed space to Scroll Content Manager, following the instructions provided in this article: [Convert a Space to Scroll Content Manager](https://migration.k15t.com/scroll-apps/migration/convert-a-space-to-scroll-documents.md) 2. Migrate your new Scroll Content Manager managed space to your new Data Center or Cloud Confluence system. 3. Access your new Confluence system. 4. Create a new space with the same space key as the original space. 5. Navigate to the migrated space. 6. Transfer the pages and document metadata to the newly created space, as explained in this article[: Move a Document](https://help.k15t.com/scroll-docs?contextKey=k15t-docs-move-document&version=latest&variant=default) 7. Verify that all content has been successfully moved to the new space as expected. 8. Delete the now empty space that was created during the conversion from Scroll Versions or Scroll Translations to Scroll Content Manager. --- version: "v4" language: "en" --- # How to Read the Migration Report in JSON Format We recommend you run the Migration Report before converting to Scroll Content Manager. Its aim is to help you understand which features of Scroll Versions or Scroll Translations are used in your spaces. In this article, you'll learn more about how to read the JSON file which is generated when you run the report. This article will also help clarify how well Scroll Content Manager supports the features you are currently using. The JSON report provides additional details beyond the migration report generated within the Confluence UI. To gain a deeper understanding of how to read the results directly within Confluence, please refer to: [Run the Migration Report](https://migration.k15t.com/scroll-apps/migration/run-the-migration-report.md) ## Understand the Different Parts of the Report The overall report consists of two main parts: * The `spaces` report * The `system` report You'll learn more about these individual parts of the report below. ### The spaces report The `spaces` report is the biggest part of the overall migration report and is divided into three parts per space: | **Part** | **What information you'll find** | |-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `pages` | This part of the report gives you information about all pages in this space. | | `macros` | This part lists all macros that are used in this space. You'll find information about third-party macros, as well as macros from our Scroll apps. For tips on which specific Scroll macros to look out for,[jump down to the section below](https://migration.k15t.com/scroll-apps/migration/how-to-read-the-migration-report-in-json-format.md#macros) ⬇️ | | `scroll-platform` | In this part you'll find out which features of Scroll Versions and Scroll Translations you are using in the space, and to what extent, for example, how many versions, variants, or languages the space has. | #### Which macros to look out for In the macro part of the space report, we recommend keeping an eye out for the following Scroll macros: | **Scroll macro** | **Are these macros supported in the conversion?** | **What happens to this macro in Scroll Content Manager?** | |----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Include+ | Yes ![check mark](https://migration.k15t.com/__attachments/a_df3fd5a38dbc956984ffb635c888011595d3a7cc5a3deb0d6e58cfcb0d874fc7/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | Include+ and Excerpt Include+ will be transformed into their Confluence counterparts ([Include Page](https://support.atlassian.com/confluence-cloud/docs/insert-the-include-page-macro/)and [Excerpt Include](https://support.atlassian.com/confluence-cloud/docs/insert-the-excerpt-include-macro/)) when you convert the space to Scroll Content Manager | | Excerpt Include+ | Yes ![check mark](https://migration.k15t.com/__attachments/a_df3fd5a38dbc956984ffb635c888011595d3a7cc5a3deb0d6e58cfcb0d874fc7/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | Include+ and Excerpt Include+ will be transformed into their Confluence counterparts ([Include Page](https://support.atlassian.com/confluence-cloud/docs/insert-the-include-page-macro/)and [Excerpt Include](https://support.atlassian.com/confluence-cloud/docs/insert-the-excerpt-include-macro/)) when you convert the space to Scroll Content Manager | | Conditional content | Yes ![check mark](https://migration.k15t.com/__attachments/a_df3fd5a38dbc956984ffb635c888011595d3a7cc5a3deb0d6e58cfcb0d874fc7/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | Any Conditional Content macro will be transformed into its counterpart in Scroll Content Manager, called Scroll Conditional Content. For more information, see: [Conversion with Conditional Content](https://migration.k15t.com/scroll-apps/migration/convert-with-conditional-content.md) | | Translations ignore | Yes ![check mark](https://migration.k15t.com/__attachments/a_df3fd5a38dbc956984ffb635c888011595d3a7cc5a3deb0d6e58cfcb0d874fc7/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | Any Translations ignore and Translations ignore inline macros are transformed into their counterparts in Scroll Content Manager: Scroll Non-Translatable and Scroll Non-Translatable Inline. You can read more about these macros here: [Mark Content as Non-Translatable](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-non-translatable&version=latest&variant=default) | | Translations ignore inline | Yes ![check mark](https://migration.k15t.com/__attachments/a_df3fd5a38dbc956984ffb635c888011595d3a7cc5a3deb0d6e58cfcb0d874fc7/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | Any Translations ignore and Translations ignore inline macros are transformed into their counterparts in Scroll Content Manager: Scroll Non-Translatable and Scroll Non-Translatable Inline. You can read more about these macros here: [Mark Content as Non-Translatable](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-non-translatable&version=latest&variant=default) | . If you are using: * [Scroll PDF Exporter](https://marketplace.atlassian.com/apps/7019/scroll-pdf-exporter-for-confluence?hosting=cloud&tab=overview), * [Scroll Word Exporter](https://marketplace.atlassian.com/apps/24982/scroll-word-exporter-for-confluence?hosting=cloud&tab=overview), * or [Scroll HTML Exporter](https://marketplace.atlassian.com/apps/420604/scroll-html-exporter-for-confluence?hosting=cloud&tab=overview) you may also find some macros from the[Scroll Exporter Extensions](https://help-cloud.k15t.com/scroll-exporter-extensions/1.0/) listed in the report, such as the Scroll Pagetitle macro. If you are planning a migration to Cloud, we recommend you take a look at the following article for how to migrate the Exporter macros: [Migration path](https://help.k15t.com/scroll-exporter-extensions?contextKey=migration-path&version=latest&variant=default) ### The system report In the `system` part of the report you'll find information about: * Which of K15t's Scroll apps you have installed. * Which app versions you are using. We try to improve the conversion path to Scroll Content Manager with every new release. If you are converting from Scroll Versions and/ or Scroll Translation to Scroll Content Manager, we recommend using the latest versions of the apps. To find the latest versions you can take a look at their latest Marketplace releases: * [Scroll Versions for Confluence](https://marketplace.atlassian.com/apps/1210818/scroll-versions-for-confluence/version-history) * [Scroll Translations for Confluence](https://marketplace.atlassian.com/apps/1211616/scroll-translations-for-confluence/version-history) * [Scroll Content Manager for Confluence](https://marketplace.atlassian.com/apps/1217608/scroll-documents-for-confluence/version-history) If you don't use [Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview), we recommend taking a look. Scroll Content Manager integrates with Scroll Sites on Confluence Cloud, enabling you to create versioned or translated online help centers. For more information see: [Create and Manage Product Documentation in Confluence](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) ## How to Read the Report In the table below, we have listed the different entries you'll find in the overall report. You'll learn what each entry means, and if you're required to take any action when given a specific value. A required action refers to a task you are recommended to take before converting to Scroll Content Manager. | **Report entry** | **This entry tells you...** | **Required actions** | **Additional recommendations** | |---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `spaceKey` | The [space key](https://support.atlassian.com/confluence-cloud/docs/choose-a-space-key/) of the space. | No action required | When converting to Scroll Content Manager, you'll create a new Scroll Content Manager-managed copy of the original space. In this case, you'll need to consider if you want to define a new space key. If you want to keep the same space key, have a look at this article: [How to Keep the Old Space Key after Converting to Scroll Content Manager](https://migration.k15t.com/scroll-apps/migration/how-to-keep-the-old-space-key-after-migration-to-1.md) | | `spaceName` | The name of the space | No action required | - | | `archived` | If the value shows `true` this mean the space has been[archived](https://support.atlassian.com/confluence-cloud/docs/archive-a-space/). | Double check if you want to keep the space and convert it to Scroll Content Manager. | We recommend taking the conversion as a chance to clean up old spaces and avoid migrating archived spaces to Cloud. | | `personal` | If the value shows `true` this means this is a [personal space](https://confluence.atlassian.com/doc/create-your-personal-space-777010869.html). | Double check with the space owner if they want to convert this space to Scroll Content Manager. Alternatively, check whether Scroll Versions or Scroll Translations can be deactivated. | - | | `topLevelPages` | How many top-level pages this space has. In other words, how many pages are on the highest level in the space. | If the value is greater than one, this means you have more than one top-level page in the space. In this case, before converting: Go to **Space tools** \> **Reorder pages**and place all pages in the page tree under the same top-level page. You won't be able to convert to Scroll Content Manager until this requirement is fulfilled. | Due to the way that the app works, Scroll Content Manager needs all pages to be stored under a single page, which is why you need to potentially reorder the page. | | `pages` | How many pages exist in this space. | If your space has a lot of pages, take this as an opportunity to clean up the space by removing outdated or redundant content | - | | `blogPosts` | How many blog posts have been created in this space. | No action required **To keep in mind:** When converting spaces, blog posts are copied to the new space, but keep in mind: * Only the latest revision is copied. * Original creator and creation date are retained. * Last modification date is set to the conversion date. * The last modifier is set to the user who initiated the conversion. | - | | `isPlatformEnabled` | If the value shows `true` , this means the 'Scroll Platform' app is enabled in your Confluence system. Scroll Platform comes bundled with Scroll Versions and Scroll Translations. It is important Scroll Platform is enabled, as it contains code which helps Scroll Versions and Scroll Translations work as expected. | No action required | - | | `isAnyVersionsModuleEnabled` | If the value shows `true` this means Scroll Versions' features are used in this space. | Continue going through the report to find out which features are used, and how those features work in Scroll Content Manager | - | | `isVersionsEnabled` | If the value shows `true` this means at least one version has been created in this space. | Versions are managed differently in Scroll Versions and Scroll Content Manager. We recommend learning more about this before converting. See: [Manage Versions](https://migration.k15t.com/scroll-apps/migration/manage-versions.md) | - | | `isVariantsEnabled` | If the value shows `true` this means the space contains at least one variant. | Variant management works differently in Scroll Content Manager than in Scroll Versions. It's good to learn more about these differences before converting. You can find more information here: [Manage Variants and Conditional Content](https://migration.k15t.com/scroll-apps/migration/manage-variants-and-conditional-content.md) | - | | `isAllVariantVisibleInViewport` | If the value shows `true` this means the space and its variants are available in Scroll Viewport / Scroll Sites | No action required | - | | `isTranslationsEnabled` | If the value shows `true` this means you have translations of your content in this space. | The concept and workflow of translations in Scroll Content Manager works differently than Scroll Translations. We recommend learning more about this before converting. See: * [Manage a Translated Space](https://migration.k15t.com/scroll-apps/migration/manage-a-translated-space.md) * [Manage Manual and External Translations](https://migration.k15t.com/scroll-apps/migration/manual-and-external-translations.md) | - | | `isOnlyTranslationsEnabled` | If the value shows `true` this means the space is only using Scroll Translations. | The concept and workflow of translations in Scroll Content Manager works differently than Scroll Translations. We recommend learning more about this before converting. See: * [Manage a Translated Space](https://migration.k15t.com/scroll-apps/migration/manage-a-translated-space.md) * [Manage Manual and External Translations](https://migration.k15t.com/scroll-apps/migration/manual-and-external-translations.md) | With Scroll Content Manager and Translations for Scroll Content Manager we mainly focus on the [Product Documentation use case](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default). If you were using Scroll Translations to manage your intranet content in different languages, reach out to us via: [help@k15t.com](mailto:help@k15t.com) | | `isWorkflowEnabled` | If the value shows `true` this means workflows are used in this space. | Continue in the report to see what type of workflow is used. | We will be looking into the possibility of supporting an integration with Comala in the future. If you're interested, follow the progress here: [DOCS-36](https://k15t.jira.com/browse/DOCS-36) | | `isSimpleWorkflowEnabled` | If the value shows `true` this means you are using Scroll Versions'[inbuilt workflow](https://help-cloud.k15t.com/scroll-versions/?contextKey=workflows-intro&version=latest&variant=default) in this space. | Scroll Content Manager has its own built-in workflow feature, but it does **not**yet integrate with Comala Document Management. We recommend reading: * [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) * [Workflow Statuses After Conversion](https://migration.k15t.com/scroll-apps/migration/workflow-statuses-after-conversion.md) It's currently not possible to convert a Scroll Versions workflow into a Scroll Content Manager workflow during the conversion process. | We will be looking into the possibility of supporting an integration with Comala in the future. If you're interested, follow the progress here: [DOCS-36](https://k15t.jira.com/browse/DOCS-36) | | `isComalaWorkflowEnabled` | If the value shows `true` this means the space uses Scroll Versions and [Comala Document Management](https://marketplace.atlassian.com/apps/142/comala-document-management?hosting=cloud&tab=overview) to manage workflows. | Scroll Content Manager has its own built-in workflow feature, but it does **not**yet integrate with Comala Document Management. We recommend reading: * [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) * [Workflow Statuses After Conversion](https://migration.k15t.com/scroll-apps/migration/workflow-statuses-after-conversion.md) It's currently not possible to convert a Scroll Versions workflow into a Scroll Content Manager workflow during the conversion process. | We will be looking into the possibility of supporting an integration with Comala in the future. If you're interested, follow the progress here: [DOCS-36](https://k15t.jira.com/browse/DOCS-36) | | `isPermalinkSupport` | If the value shows `true` this mean this space is using [Duplicate page titles](https://help-cloud.k15t.com/scroll-versions/?contextKey=duplicate-page-titles&version=latest&variant=default). | Scroll Content Manager supports duplicate page titles, but in a different way than what you're used to in Scroll Versions. We recommend reading the following articles for more information about the differences, and how they are converted: * [Conversion with Duplicate Page Titles](https://migration.k15t.com/scroll-apps/migration/conversion-with-duplicate-page-titles.md) * [How to Convert a Space with Duplicate Page Titles](https://migration.k15t.com/scroll-apps/migration/how-to-convert-a-space-with-duplicate-page-titles.md) | Learn more about how you can work with duplicate page titles in Scroll Content Manager using prefixes and a Scroll Page Title: * [Edit Version Prefix](https://help-cloud.k15t.com/scroll-docs?contextKey=k15t-docs-help-edit-instance-props&version=latest&variant=default) * [Add Scroll Page Titles](https://help.k15t.com/scroll-doc/?contextKey=add-scroll-page-titles&version=latest&variant=default) * [Can I Use the Same Page Title Multiple Times in a Document?](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-scroll-page-title&version=latest&variant=default) | | `isSeoEnabled` | If the value shows `true` it means the SEO feature is enabled in this space. | No action required **Keep in mind** The SEO feature is **not** supported in Scroll Content Manager. If you want to work with online documentation on Cloud, we recommend combining Scroll Content Manager with Scroll Sites. For more information see: [Create and Manage Product Documentation in Confluence](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) | - | | `isRestrictEditInReaderView` | If the value shows `true` it means you have restricted edit permissions to the [Public View](https://help.k15t.com/scroll-versions/4.5/glossary#id-(4.5)Glossary-PublicViewPublic-View). | No action required **Keep in mind** The concept of Public View does **not** exist in Scroll Content Manager. If you want to publish content to a public audience, consider combining Scroll Content Manager with [Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview). For more information see: [Create and Manage Product Documentation in Confluence](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) | - | | `isSearchEnabled` | If the value shows `true` this means [Scroll Search](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-search&version=latest&variant=default)is enabled in this space. | No action required **Keep in mind** Scroll Search does **not** exist in Scroll Content Manager. When searching for specific pages in Confluence you would need to search with version and/ or language prefixes to find a specific page in a specific version. In [Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview) it's enough to search for the page name and work with manual filters for versions, variants, and languages. | - | | `isTargetSpace` | If the value shows `true` this means languages have been published to the space. | If it's a target space, consider whether you really need it. To help you make an informed decision, we recommend reading [Conversion with Target Spaces.](https://migration.k15t.com/scroll-apps/migration/convert-a-target-space.md) | - | | `isVersionedSpace` | If the value shows `true` this means Scroll Versions has been used to create versions in this space. | Versions are managed differently in Scroll Versions and Scroll Content Manager. We recommend learning more about this before converting. See: [Manage Versions](https://migration.k15t.com/scroll-apps/migration/manage-versions.md) | - | | `hasOutgoingSpaceLinks` | If the value shows `true` , this means this is a documentation space which reuses content from other spaces via an [Include Library](https://help-cloud.k15t.com/scroll-versions/?contextKey=content-reuse&version=latest&variant=default). | The [Include Library feature](https://help-cloud.k15t.com/scroll-versions/?contextKey=content-reuse&version=latest&variant=default) is currently not fully supported in Scroll Content Manager. As it works currently, the included content will instead be converted in the new Scroll Content Manager managed space. Learn more: [Conversion with Include Libraries](https://migration.k15t.com/scroll-apps/migration/conversion-with-include-libraries.md) The source pages of the included content will be copied and added to the top-level above the home page. | If the outcome described does not fulfill your requirements, we recommend waiting to convert and reaching out to our support via: [help@k15t.com](mailto:help@k15t.com) | | `hasIncomingSpaceLinks` | If the value shows `true` this means this space is an [Include Library](https://help-cloud.k15t.com/scroll-versions/?contextKey=content-reuse&version=latest&variant=default). The content from this space is included in other spaces / documentation spaces. | The [Include Library feature](https://help-cloud.k15t.com/scroll-versions/?contextKey=content-reuse&version=latest&variant=default) is currently not fully supported in Scroll Content Manager. As it works currently, the included content will instead be converted in the new Scroll Content Manager managed space. Learn more: [Conversion with Include Libraries](https://migration.k15t.com/scroll-apps/migration/conversion-with-include-libraries.md) The source pages of the included content will be copied and added to the top-level above the home page. | If the outcome described does not fulfill your requirements, we recommend waiting to convert and reaching out to our support via: [help@k15t.com](mailto:help@k15t.com) | | `hasRoles` | If the value shows `true` this means [Scroll Roles](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-roles&version=latest&variant=default) are used in this space. | [Scroll Roles](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-roles&version=latest&variant=default) are not supported in Scroll Content Manager. In Scroll Content Manager, we recommend working with version restrictions and the comparison tool to maintain an author and review process. See: [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) **Keep in mind** Restrictions set via Scroll Roles or edit restrictions on specific versions are removed in the conversion. | Remember to re-apply potentially important restrictions after the conversion. For more information about restriction and permissions handling in Scroll Content Manager see: * [Manage Restrictions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-permissions&version=latest&variant=default) * [Assign the Required Permissions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-space-permissions&version=latest&variant=default) | | `hasPermalinks` | If the value shows `true` this means the space has [permalinks](https://help-cloud.k15t.com/scroll-versions/?contextKey=difference-between-permalinks-and-page-keys&version=latest&variant=default) and is using [Duplicate page titles](https://help-cloud.k15t.com/scroll-versions/?contextKey=duplicate-page-titles&version=latest&variant=default). | Scroll Content Manager supports duplicate page titles, but in a different way than what you're used to in Scroll Versions. We recommend reading the following articles for more information about the differences, and how they are converted: * [Scroll Versions and Scroll Content Manager Compared](https://migration.k15t.com/scroll-apps/migration/scroll-versions-and-scroll-documents-compared.md) * [Conversion with Duplicate Page Titles](https://migration.k15t.com/scroll-apps/migration/conversion-with-duplicate-page-titles.md) | Learn more about how you can work with duplicate page titles in Scroll Content Manager using prefixes and a Scroll Page Title: * [Edit Version Prefix](https://help-cloud.k15t.com/scroll-docs?contextKey=k15t-docs-help-edit-instance-props&version=latest&variant=default) * [Add Scroll Page Titles](https://help.k15t.com/scroll-doc/?contextKey=add-scroll-page-titles&version=latest&variant=default) * [Can I Use the Same Page Title Multiple Times in a Document?](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-scroll-page-title&version=latest&variant=default) | | `hasPageKeys` | If the value shows `true` this means the space uses [Page keys](https://help-cloud.k15t.com/scroll-versions/?contextKey=difference-between-permalinks-and-page-keys&version=latest&variant=default). | Page keys can be used to create stable links that reference specific versions in Confluence and[Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview). This feature can be converted to Scroll Content Manager, but is referred to as Context Keys. To learn more, see: [Assign Context Keys](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-context-keys&version=latest&variant=default) | - | | `incomingLinks` | This value shows the amount of incoming links from other spaces that point to pages in this space. | If your Scroll Versions or Scroll Translations-managed space has incoming links from other spaces in your Confluence system, you can choose to rewrite those links so they point to the newly converted Scroll Content Manager space. To learn more, see: [Migration of Incoming Links](https://migration.k15t.com/scroll-apps/migration/migration-of-incoming-links.md) Any page that had its link rewritten during this action will be listed in the Confluence logs with its page ID for reference. | - | | `hasVersions` | If the value shows `true` this means [space versions](https://help-cloud.k15t.com/scroll-versions/?contextKey=intro-version-management&version=latest&variant=default) have been defined in this space. | Versions are managed differently in Scroll Versions and Scroll Content Manager. We recommend learning more about this before converting. See: [Manage Versions](https://migration.k15t.com/scroll-apps/migration/manage-versions.md) | - | | `hasVariants` | If the value shows `true` this means the space has [variants](https://help-cloud.k15t.com/scroll-versions/?contextKey=intro-conditional-content-variants&version=latest&variant=default)defined. | Variant management works differently in Scroll Content Manager. We recommend learning more about this before converting: [Manage Variants and Conditional Content](https://migration.k15t.com/scroll-apps/migration/manage-variants-and-conditional-content.md) | - | | `hasLanguages` | If the value shows `true` this means there are space [languages](https://help-cloud.k15t.com/scroll-translations/?contextKey=get-started&version=latest&variant=default) defined. | The concept and workflow of translations in Scroll Content Manager works differently than Scroll Translations. We recommend learning more about this before converting: * [Manage a Translated Space](https://migration.k15t.com/scroll-apps/migration/manage-a-translated-space.md) * [Manage Manual and External Translations](https://migration.k15t.com/scroll-apps/migration/manual-and-external-translations.md) | - | | `isUnrecommendedFeatureIncludeLibraryEnabled` | If the value shows `true` this means the[](https://help-cloud.k15t.com/scroll-versions/4.5/intro-to-content-reuse)[Include Library](https://help-cloud.k15t.com/scroll-versions/?contextKey=content-reuse&version=latest&variant=default) feature might be in use in this space. | Continue to the report entries `hasOutgoingSpaceLinks` and `hasIncomingSpaceLinks` to confirm if this space is a part of an Include Library. | **Note for Scroll Versions and Scroll Translations 4.5.0 users** When enabling Scroll Versions or Scroll Translations in a new space, you may observe that these features are disabled. For more information, please refer to the release notes for [Scroll Versions 4.5.0](https://help-cloud.k15t.com/scroll-versions/4.5/scroll-versions-4-5-0). | | `isUnrecommendedFeatureRolesEnabled` | If the value shows `true` this means [Scroll Roles](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-roles&version=latest&variant=default) might be in use in this space. | Continue to the report entry `hasRoles` to confirm if you are actively using Scroll Roles in this space. | **Note for Scroll Versions and Scroll Translations 4.5.0 users** When enabling Scroll Versions or Scroll Translations in a new space, you may observe that these features are disabled. For more information, please refer to the release notes for [Scroll Versions 4.5.0](https://help-cloud.k15t.com/scroll-versions/4.5/scroll-versions-4-5-0). | | `isUnrecommendedFeatureRestrictEditInReaderViewEnabled` | If the value shows `true` this means the option to edit the [Public View](https://help.k15t.com/scroll-versions/4.5/glossary#id-(4.5)Glossary-PublicViewPublic-View) might be in use in this space. | Continue to the report entry `publishedVersionInfos` to confirm how you are publishing your content. | **Note for Scroll Versions and Scroll Translations 4.5.0 users** When enabling Scroll Versions or Scroll Translations in a new space, you may observe that these features are disabled. For more information, please refer to the release notes for [Scroll Versions 4.5.0](https://help-cloud.k15t.com/scroll-versions/4.5/scroll-versions-4-5-0). | | `isUnrecommendedFeaturePublishToSameEnabled` | If the value shows `true` this means the option to [publish within the same space](https://help-cloud.k15t.com/scroll-versions/?contextKey=publish-same&version=latest&variant=default) might be in use in this space. | Continue to the report entry `publishedVersionInfos` to confirm how you are publishing your content. | **Note for Scroll Versions and Scroll Translations 4.5.0 users** When enabling Scroll Versions or Scroll Translations in a new space, you may observe that these features are disabled. For more information, please refer to the release notes for [Scroll Versions 4.5.0](https://help-cloud.k15t.com/scroll-versions/4.5/scroll-versions-4-5-0). | | `containsMultipleRootVersions` | If the value shows `true` this means the version tree in the space has several root versions. | Multiple root versions is a legacy feature in an older version of Scroll Versions. If you find you have multiple root versions, reach out to: [help@k15t.com](mailto:help@k15t.com) | - | | `containsBranches` | If the value shows `true` this means the version tree consists of several branches. | No action required **Keep in mind** It's not possible to create branches in Scroll Content Manager. Your existing version branches will be converted into a linear version tree within Scroll Content Manager. | - | | `numberOfVersions ` | How many versions the space has. | If the space has many versions, consider whether you really need to convert all versions. **Note** In Scroll Content Manager, the amount of pages in the space will be multiplied by the amount of versions and languages you have in the space. In short, if you have a lot of pages, versions, and/ or languages this will affect space size and the performance of document-wide actions like comparing versions. | - | | `numberOfRootVersions` | If the version tree has several root versions, this value tells you how many root versions the version tree has. | Multiple root versions is a legacy feature in an older version of Scroll Versions. If you find you have multiple root versions, reach out to: [help@k15t.com](mailto:help@k15t.com) | - | | `numberOfBranches` | If the version tree has several branches, this value tells you how many branches. | No action required **Keep in mind** In Scroll Content Manager it's**not** possible to create branches. Your existing version branches will be converted into a linear version tree within Scroll Content Manager | - | | `publishedVersionInfos` | How this space has been published. You'll find one entry per different publishing method. If you published within the same space it looks like this: * `remoteSystemId: null` * `targetSpaceKey: ` If you published to a new or existing space it looks like this: * `remoteSystemId: null` * `targetSpaceKey: ` If you have not published the space with Scroll Versions it looks like this: * `publishedVersionInfos: []` If you published to a remote system it looks like this: * `remoteSystemId: <"nbjb8385-juzd-992d-ad72-ebd8764dji89">` * `targetSpaceKey: ` | With Scroll Content Manager you can publish content to a specific target space, or a parent page within your authoring space. However remote publishing to other Confluence systems is **not** available in Scroll Content Manager. This is also **not**something we are planning to implement. As an alternative solution to remote publishing we recommend that you [publish your document as an online help center](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) with [Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview). | For more information about publishing to Confluence with Scroll Content Manager, see: [Publish Versions and Variants](https://migration.k15t.com/scroll-apps/migration/publish-versions-and-variants.md) | | `hasPublished` | If the space has been [published](https://help-cloud.k15t.com/scroll-versions/?contextKey=publish-in-confluence&version=latest&variant=default). | With Scroll Content Manager you can publish content to a specific target space, or a parent page within your authoring space. However remote publishing to other Confluence systems is **not** available in Scroll Content Manager. This is also **not**something we are planning to implement. As an alternative solution to remote publishing we recommend that you [publish your document as an online help center](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) with [Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview). | - | | `hasPublishedToSame` | If the space has been published with [within same space](https://help-cloud.k15t.com/scroll-versions/?contextKey=publish-same&version=latest&variant=default). | With Scroll Content Manager you can publish content to a specific target space, or a parent page within your authoring space. However remote publishing to other Confluence systems is **not** available in Scroll Content Manager. This is also **not**something we are planning to implement. As an alternative solution to remote publishing we recommend that you [publish your document as an online help center](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) with [Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview). | - | | `hasPublishedToNew` | If the space has been published [to a new space](https://help-cloud.k15t.com/scroll-versions/?contextKey=publish-new&version=latest&variant=default). | With Scroll Content Manager you can publish content to a specific target space, or a parent page within your authoring space. However remote publishing to other Confluence systems is **not** available in Scroll Content Manager. This is also **not**something we are planning to implement. As an alternative solution to remote publishing we recommend that you [publish your document as an online help center](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) with [Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview). | - | | `hasPublishedToExisting` | If the space has been published [to an existing space](https://help-cloud.k15t.com/scroll-versions/?contextKey=publish-existing&version=latest&variant=default). | With Scroll Content Manager you can publish content to a specific target space, or a parent page within your authoring space. However remote publishing to other Confluence systems is **not** available in Scroll Content Manager. This is also **not**something we are planning to implement. As an alternative solution to remote publishing we recommend that you [publish your document as an online help center](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) with [Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview). | - | | `hasPublishedToRemote` | If the space has been published [to a remote system](https://help-cloud.k15t.com/scroll-versions/?contextKey=publish-remote&version=latest&variant=default). | With Scroll Content Manager you can publish content to a specific target space, or a parent page within your authoring space. However remote publishing to other Confluence systems is **not** available in Scroll Content Manager. This is also **not**something we are planning to implement. As an alternative solution to remote publishing we recommend that you [publish your document as an online help center](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) with [Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview). | - | | `variants` | If the space has variants, this value tells you how many variants the space has, as well as how many attributes and attribute values you have defined. See example below: * `numberOfVariants`: x * `numberOfAttributes`: x * `numberOfAttributeValues`: x | Variant management works differently in Scroll Content Manager. We recommend learning more about this before converting: [Manage Variants and Conditional Content](https://migration.k15t.com/scroll-apps/migration/manage-variants-and-conditional-content.md) | - | | `numberOfLanguages` | How many languages are in the space. | If the space has many languages, consider whether it makes sense to convert all of them. **Note** In Scroll Content Manager, the amount of pages in the space will be multiplied by the amount of versions and languages you have in the space. In short, if you have a lot of pages, versions, and / or languages this will affect space performance and make the document more difficult to manage. | - | | `permalinks` | Amount of pages using [Duplicate page titles](https://help-cloud.k15t.com/scroll-versions/?contextKey=duplicate-page-titles&version=latest&variant=default). You'll also get a list showing: * if any of the pages has any [permalinks](https://help-cloud.k15t.com/scroll-versions/?contextKey=difference-between-permalinks-and-page-keys&version=latest&variant=default) related errors, * the Confluence page title of the individual pages, * the [Scroll page title](https://help-cloud.k15t.com/scroll-versions/?contextKey=difference-between-permalinks-and-page-keys&version=latest&variant=default) of the pages, * the exact permalink the pages are using, * their Confluence page ID, * and if the pages have any [page keys](https://help-cloud.k15t.com/scroll-versions/?contextKey=use-page-keys&version=latest&variant=default). See example below: * `errors` : x * `numberOf` : x * `confluencePageTitle` : x * `permalink` : x * `scrollPageTitle` : x * `confluencePageId` : x * `pageKey` : x | Scroll Content Manager supports duplicate page titles, but in a different way than what you're used to in Scroll Versions. We recommend reading the following articles for more information about the differences, and how they are converted: * [Scroll Versions and Scroll Content Manager Compared](https://migration.k15t.com/scroll-apps/migration/scroll-versions-and-scroll-documents-compared.md) * [Conversion with Duplicate Page Titles](https://migration.k15t.com/scroll-apps/migration/conversion-with-duplicate-page-titles.md) | Learn more about how you can work with duplicate page titles in Scroll Content Manager using prefixes and a Scroll Page Title: * [Edit Version Prefix](https://help-cloud.k15t.com/scroll-docs?contextKey=k15t-docs-help-edit-instance-props&version=latest&variant=default) * [Add Scroll Page Titles](https://help.k15t.com/scroll-doc/?contextKey=add-scroll-page-titles&version=latest&variant=default) * [Can I Use the Same Page Title Multiple Times in a Document?](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-scroll-page-title&version=latest&variant=default) | | `pageKeys` | Amount of [Page keys](https://help-cloud.k15t.com/scroll-versions/?contextKey=use-page-keys&version=latest&variant=default) in the space. You'll also get a list showing: * if any of the pages has any page key related errors, * the Confluence page title of the individual pages, * the [Scroll page title](https://help-cloud.k15t.com/scroll-versions/?contextKey=difference-between-permalinks-and-page-keys&version=latest&variant=default) of the pages, * the [permalink](https://help-cloud.k15t.com/scroll-versions/?contextKey=difference-between-permalinks-and-page-keys&version=latest&variant=default) of the pages (if this has been defined), * their Confluence page ID, * and the exact page key the page is using. * `errors` : x * `numberOf` : x * `confluencePageTitle` : x * `permalink` : x * `scrollPageTitle` : x * `confluencePageId` : x * `pageKey` : x | Page keys can be used to create stable links that reference specific versions in Confluence and[Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview). This feature can be converted to Scroll Content Manager, but is referred to as Context Keys. To learn more see: [Assign Context Keys](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-context-keys&version=latest&variant=default) | - | | `numberOfAuthorGroupNames` | How many groups have been defined within the Author role. | [Scroll Roles](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-roles&version=latest&variant=default) are not supported in Scroll Content Manager. In Scroll Content Manager, we recommend working with version restrictions and the comparison tools to maintain an author and review process. See: [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) **Keep in mind** Restrictions set via Scroll Roles or edit restrictions on specific versions are resolved in the conversion. | Remember to re-apply potentially important restrictions after the conversion. For more information about restriction and permissions handling in Scroll Content Manager see: * [Manage Restrictions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-permissions&version=latest&variant=default) * [Assign the Required Permissions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-space-permissions&version=latest&variant=default) | | `numberAuthorUserKeys` | How many individual users have been assigned the Author role. | [Scroll Roles](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-roles&version=latest&variant=default) are not supported in Scroll Content Manager. In Scroll Content Manager, we recommend working with version restrictions and the comparison tools to maintain an author and review process. See: [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) **Keep in mind** Restrictions set via Scroll Roles or edit restrictions on specific versions are resolved in the conversion. | Remember to re-apply potentially important restrictions after the conversion. For more information about restriction and permissions handling in Scroll Content Manager see: * [Manage Restrictions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-permissions&version=latest&variant=default) * [Assign the Required Permissions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-space-permissions&version=latest&variant=default) | | `numberOfDocAdminGroupNames` | How how many groups have been defined within the Doc-admin role. | [Scroll Roles](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-roles&version=latest&variant=default) are not supported in Scroll Content Manager. In Scroll Content Manager, we recommend working with version restrictions and the comparison tools to maintain an author and review process. See: [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) **Keep in mind** Restrictions set via Scroll Roles or edit restrictions on specific versions are resolved in the conversion. | Remember to re-apply potentially important restrictions after the conversion. For more information about restriction and permissions handling in Scroll Content Manager see: * [Manage Restrictions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-permissions&version=latest&variant=default) * [Assign the Required Permissions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-space-permissions&version=latest&variant=default) | | `numberOfDocAdminUserKeys` | How many individual users have been assigned the Doc-admin role. | [Scroll Roles](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-roles&version=latest&variant=default) are not supported in Scroll Content Manager. In Scroll Content Manager, we recommend working with version restrictions and the comparison tools to maintain an author and review process. See: [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) **Keep in mind** Restrictions set via Scroll Roles or edit restrictions on specific versions are resolved in the conversion. | Remember to re-apply potentially important restrictions after the conversion. For more information about restriction and permissions handling in Scroll Content Manager see: * [Manage Restrictions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-permissions&version=latest&variant=default) * [Assign the Required Permissions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-space-permissions&version=latest&variant=default) | | `numberOfReviewerGroupNames` | How many groups have been defined within the Reviewer role. | [Scroll Roles](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-roles&version=latest&variant=default) are not supported in Scroll Content Manager. In Scroll Content Manager, we recommend working with version restrictions and the comparison tools to maintain an author and review process. See: [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) **Keep in mind** Restrictions set via Scroll Roles or edit restrictions on specific versions are resolved in the conversion. | Remember to re-apply potentially important restrictions after the conversion. For more information about restriction and permissions handling in Scroll Content Manager see: * [Manage Restrictions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-permissions&version=latest&variant=default) * [Assign the Required Permissions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-space-permissions&version=latest&variant=default) | | `numberOfReviewerUserKeys` | How many individual users have been assigned the Reviewer role. | [Scroll Roles](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-roles&version=latest&variant=default) are not supported in Scroll Content Manager. In Scroll Content Manager, we recommend working with version restrictions and the comparison tools to maintain an author and review process. See: [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) **Keep in mind** Restrictions set via Scroll Roles or edit restrictions on specific versions are resolved in the conversion. | Remember to re-apply potentially important restrictions after the conversion. For more information about restriction and permissions handling in Scroll Content Manager see: * [Manage Restrictions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-permissions&version=latest&variant=default) * [Assign the Required Permissions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-space-permissions&version=latest&variant=default) | | `numberOfTranslatorGroupNames` | How many groups have been defined within the Translator role. | [Scroll Roles](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-roles&version=latest&variant=default) are not supported in Scroll Content Manager. In Scroll Content Manager, we recommend working with version restrictions and the comparison tools to maintain an author and review process. See: [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) **Keep in mind** Restrictions set via Scroll Roles or edit restrictions on specific versions are resolved in the conversion. | Remember to re-apply potentially important restrictions after the conversion. For more information about restriction and permissions handling in Scroll Content Manager see: * [Manage Restrictions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-permissions&version=latest&variant=default) * [Assign the Required Permissions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-space-permissions&version=latest&variant=default) | | `numberOfTranslatorUserKeys` | How many individual users have been assigned the Translator role. | [Scroll Roles](https://help-cloud.k15t.com/scroll-versions/?contextKey=scroll-roles&version=latest&variant=default) are not supported in Scroll Content Manager. In Scroll Content Manager, we recommend working with version restrictions and the comparison tools to maintain an author and review process. See: [Compare, Track, and Review Versions and Variants](https://migration.k15t.com/scroll-apps/migration/compare-track-and-review-versions-and-variants.md) **Keep in mind** Restrictions set via Scroll Roles or edit restrictions on specific versions are resolved in the conversion. | Remember to re-apply potentially important restrictions after the conversion. For more information about restriction and permissions handling in Scroll Content Manager see: * [Manage Restrictions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-permissions&version=latest&variant=default) * [Assign the Required Permissions](https://help-cloud.k15t.com/scroll-docs/?contextKey=k15t-docs-help-space-permissions&version=latest&variant=default) | | `numberOfConditionalContentMacrosWithInlineIssues` | If the value is `1` or higher, it means there are one or more Conditional Content (Inline) macros in the space that contain content or formatting not supported by the corresponding Scroll Conditional Content Inlinemacro in Scroll Content Manager. This may impact how the content is converted. | For any space reported with a value of `1`or higher, navigate to the affected space and [run a Scroll Health Check](https://migration.k15t.com/scroll-apps/migration/run-a-first-scroll-health-check.md). This will identify the pages that contain unsupported inline Conditional Content macros. Once identified, you can decide how to handle the affected content. To learn more about your options and what this means for your conversion, see: [Conversion with Conditional Content](https://migration.k15t.com/scroll-apps/migration/convert-with-conditional-content.md) | - | To learn how to generate the report, proceed to: [How to Create the Migration Report](https://migration.k15t.com/scroll-apps/migration/how-to-create-the-migration-report.md) --- version: "v4" language: "en" --- # Introduction Atlassian has announced the [end of life for Confluence Data Center by March 2029](https://www.atlassian.com/blog/announcements/atlassian-ascend). This transition also impacts Data Center apps, including **Scroll Versions** and **Scroll Translations**. If your team is using these apps, you're not alone -- and K15t is here to guide you through every step of the journey. ## Helping You Switch with the Scroll Apps Migration Hub Welcome to the Scroll Apps Migration Hub, your go-to resource for a smooth transition from Scroll Versions and Scroll Translations to the next-generation solution: Scroll Content Manager. Whether you're moving to Cloud or preparing for other changes in your Data Center environment, our guides, tools, and step-by-step instructions make it easier to plan, assess, and execute your migration. ## Resources for Other Apps If you're planning to migrate with any of our other Confluence or Jira apps, we have helpful resources for them too: * [Scroll PDF Exporter](https://help.k15t.com/scroll-pdf-exporter/5.11/server/?contextKey=migrate-to-cloud&version=latest&variant=default) * [Scroll Word Exporter](https://help.k15t.com/scroll-word-exporter/5.11/server/?contextKey=migrate-to-cloud&version=latest&variant=default) * [Scroll HTML Exporter](https://help.k15t.com/scroll-html-exporter/3.10/server/?contextKey=migrate-to-cloud&version=latest&variant=default) * [Scroll Sites](https://help.k15t.com/scroll-viewport-data-center/?contextKey=migrate-to-cloud&version=latest&variant=default) * [Scroll Content Manager](https://help.k15t.com/scroll-docs/?contextKey=migrate-to-cloud&version=latest&variant=Data%20Center) * [Backbone Issue Sync](https://help.k15t.com/backbone-issue-sync/5.6/server?contextKey=migrate-to-cloud&version=latest&variant=default) ## Getting to Know Scroll Content Manager **Scroll Content Manager** is our next-generation solution for Confluence Cloud. Since **Scroll Versions** and **Scroll Translations** rely on Data Center infrastructure, they are now in legacy status on Cloud. Features like variants and translations are available through the extension apps: * [**Translations for Scroll Content Manager**](https://marketplace.atlassian.com/apps/1227238/translations-for-scroll-documents?hosting=cloud&tab=overview) * [**Variants for Scroll Content Manager**](https://marketplace.atlassian.com/apps/1226295/variants-for-scroll-documents?hosting=cloud&tab=overview) To migrate your legacy-managed spaces, use the inbuilt conversion paths in Scroll Versions and Scroll Translations to move to Scroll Content Manager-managed spaces. ### **What does "Legacy status" mean?** "Legacy status" means we will continue maintaining Data Center versions of Scroll Versions and Scroll Translations, focusing primarily on **compatibility and security updates**. * **If you're ready to move to Cloud:** Use Scroll Content Manager and the conversion path to migrate your content. * **If you're staying on Data Center for now:** You can continue using the legacy apps until March 2029. ## Embark on the Scroll Content Manager Journey Migrating to Scroll Content Manager involves four phases: 1. [**Understand**](https://migration.k15t.com/scroll-apps/migration/understand): Learn what's unique about Scroll Content Manager so you can make an informed decision. 2. [**Assess**](https://migration.k15t.com/scroll-apps/migration/assess): Review how your team uses Scroll Versions and Scroll Translations to decide which spaces to convert first. 3. [**Prepare**](https://migration.k15t.com/scroll-apps/migration/prepare): Clean up your spaces before converting. Removing unnecessary content makes the migration smoother. 4. [**Convert**](https://migration.k15t.com/scroll-apps/migration/convert): Follow our step-by-step conversion path to move your legacy-managed spaces to Scroll Content Manager-managed spaces. Even if you're not ready to convert yet, you can start with Understand and Assess, and begin tidying up your spaces as part of the Prepare phase. ### **Importance of Understand and Assess** Before converting, it's important to understand the differences between Scroll Content Manager and the legacy apps. While we're actively working toward feature parity, there are distinctions that may affect your workflow. Take time to assess your current usage, identify which spaces to migrate first, and plan your approach -- this makes the conversion and adoption much smoother. ## Ready to Begin? You can start exploring the four steps today. Begin by learning more about Scroll Content Manager, what happens during conversion, and how our tools guide you through the process. [**Start the Understand phase →**](https://migration.k15t.com/scroll-apps/migration/understand) --- version: "v4" language: "en" --- # Latest News ## Want to stay in touch? Sign up for email updates from K15t's Cloud Migration Hub below! [Subscribe for Updates](https://k15t.activehosted.com/f/197) Our past updates: * [Support for K15t Data Center Apps After March 2029 -August ´26](https://migration.k15t.com/scroll-apps/migration/support-for-k15t-data-center-apps-after-march-2029-august-26.md) * [A Better Health Check Experience in Conversion Process- July ´26](https://migration.k15t.com/scroll-apps/migration/a-better-health-check-experience-in-conversion-process-july-26.md) * [Cancelling Conversion Process is Now Possible - June '26](https://migration.k15t.com/scroll-apps/migration/cancelling-conversion-process-is-now-possible-june-26.md) * [Conversion Progress Now Always Visible in the UI - April ´26](https://migration.k15t.com/scroll-apps/migration/conversion-progress-now-always-visible-in-the-ui-april-26.md) * [Scroll Documents Has Been Rebranded to Scroll Content Manager - Apr '26](https://migration.k15t.com/scroll-apps/migration/scroll-documents-has-been-rebranded-to-scroll-content-manager-apr-26.md) * [A Smoother Way to Handle Space Reindexing - Mar '26](https://migration.k15t.com/scroll-apps/migration/a-smoother-way-to-handle-space-reindexing-mar-26.md) * [What to Know About Conditional Content Macros in Cloud Migrations - Nov '25](https://migration.k15t.com/scroll-apps/migration/what-to-know-about-conditional-content-macros-in-cloud-migrations-nov-25.md) * [The Enhanced Scroll Apps Migration Hub is Here! - Oct '23](https://migration.k15t.com/scroll-apps/migration/the-enhanced-scroll-apps-migration-hub-is-here-oct-23.md) * [New Feature: Enhanced Migration Report for Scroll Managed Spaces - Aug '23](https://migration.k15t.com/scroll-apps/migration/new-feature-enhanced-migration-report-for-scroll-m.md) * [Prepare for Your Migration to Scroll Documents - May'23](https://migration.k15t.com/scroll-apps/migration/prepare-for-your-migration-to-scroll-documents-may.md) * [All Paid K15t Cloud Apps Are Now Cloud Fortified - Dec'22](https://migration.k15t.com/scroll-apps/migration/all-paid-k15t-cloud-apps-are-now-cloud-fortified-d.md) * [Translations for Scroll Documents - Jun'22](https://migration.k15t.com/scroll-apps/migration/translations-for-scroll-documents-june-22.md) * [Migrate Variants to Scroll Documents - Sep'21](https://migration.k15t.com/scroll-apps/migration/migrate-variants-to-scroll-documents-sep-21.md) * [Variants in Scroll Documents - Jul'21](https://migration.k15t.com/scroll-apps/migration/variants-in-scroll-documents-jul-21.md) * [Open Cloud Migration Path for Scroll Versions Users - May'21](https://migration.k15t.com/scroll-apps/migration/open-cloud-migration-path-for-scroll-versions-user.md) * [Updated Look at the Migration Tool - Mar'21](https://migration.k15t.com/scroll-apps/migration/updated-look-at-the-migration-tool-mar-21.md) * [Cloud Roadmap and First Migration Prototype - Feb'21](https://migration.k15t.com/scroll-apps/migration/cloud-roadmap-and-first-migration-prototype-feb-21.md) --- version: "v4" language: "en" --- # Licenses for Migration When transitioning to Scroll Content Manager from our [legacy apps](https://migration.k15t.com/scroll-apps/migration/introduction.md), it is important to have Scroll Content Manager installed on your Server or Data Center system. To ensure a smooth transition, it is also advised to update all Scrolls apps to the latest version. An active license for the relevant apps is necessary to meet these requirements. For more information, you can refer to our FAQ section where frequently asked questions about this topic are answered. If you're facing difficulties installing or updating to the latest Scroll app versions because of compatibility issues with your Confluence version, don't hesitate to reach out to [help@k15t.com](mailto:help@k15t.com) for guidance. ## Does K15t Provide Licenses for the Duration of Migration? If a required app license expired during the migration preparation or if you require Data Center licenses for your migration, please reach out to us at [help@k15t.com](mailto:help@k15t.com), and we'll see what we can do to help. In particular, if you have a valid Scroll Versions DC license, we can provide a free Scroll Content Manager license with the same end date as your Scroll Versions license, so you're covered for the duration of your migration. ## What If I Need a Server License for Migration Purposes? If you need a Server license for migration purposes, a workaround would be to install a Data Center trial of that app. To do so, follow the steps below: 1. Navigate to [Atlassian Marketplace](https://marketplace.atlassian.com/). 2. Search for the relevant app. 3. Set the hosting dropdown to Data Center. 4. Click **Try it free**, and follow the steps from there. After applying the Data Center license you may see one of the following warnings: * "This app has a Data Center license, but the installed version is not Data Center compatible," * or "Wrong App Type." These warnings can be ignored, the app should still work as expected. --- version: "v4" language: "en" --- # Manage a Translated Space In this article, you'll learn how the setup of a translated space differs when it's managed by Scroll Translations versus Scroll Content Manager and Translations for Scroll Content Manager. ## Space Setup with Scroll Translations compared to Scroll Content Manager The table below outlines the differences in space setup between Scroll Translations and Scroll Content Manager: | | **A Scroll Translations managed space** | **A Scroll Content Manager managed space** | |--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Page tree** | When you activate Scroll Translations in a space, it becomes active for the entire space, and you can translate all pages within that space. | Scroll Content Manager and [its extension apps](https://migration.k15t.com/scroll-apps/migration/enhanced-variant-and-language-management-scroll-do.md) can be enabled for different scopes within the space, such as: * A single page * A subset of the space * The entire page tree What happens during conversion: * **From Scroll Translations only**: A Working version is created with all languages and existing translations. * **From Scroll Versions + Scroll Translations**: A Working version is created in the authoring language. Selected versions are recreated with their own page trees for each language. Learn more: [Manage Manual and External Translations](https://migration.k15t.com/scroll-apps/migration/manual-and-external-translations.md) | | **Language setup** | The language setup in both apps is similar. In Scroll Translations, the first language you define is the default language. In Scroll Content Manager, this is called the authoring language. All translations are based on this initial language in both apps. However, Scroll Content Manager offers more flexibility: XLIFF translations can also be created from a non-authoring language, allowing for additional translation workflows || | **Language storage** | In Scroll Translations, translations of a page are stored in dedicated language macros on the same page. These macros are usually not visible to the authors, but are automatically displayed depending on the selected language. | In Scroll Content Manager, each language has its own page tree, and translations are directly added to the Confluence page. This has the advantage that translated page titles are discoverable with Confluence search, while this is not the case with Scroll Translations managed spaces. | | **Language picker** | In Scroll Translations, you have access to a language picker in the Scroll navigation bar. In Confluence page view, you can see how the page content changes to reflect the selected language. | In Scroll Content Manager, the language picker is found in the Document toolbox and enables you to switch to a translated version of the page. Selecting a language automatically redirects you to the corresponding translation. If you want to share your translations on a public website, you can use [Scroll Sites](https://marketplace.atlassian.com/apps/1211636/scroll-viewport-for-confluence?hosting=cloud&tab=overview). To learn more, see: [Publish Translations](https://migration.k15t.com/scroll-apps/migration/publish-translations.md) | | **Translation statuses** | In Scroll Translations, you have the following translation statuses: * Translated * Outdated * Not translated | In Scroll Content Manager, there are two translation statuses which are applied as labels: * Translated * Needs-translating During the conversion to Scroll Content Manager, the previous statuses will be transformed as follows: * Translated (remains the same) * Outdated (converted to Needs-translating ) * Not translated (converted to Needs-translating ) For more information see: [Track Translations](https://migration.k15t.com/scroll-apps/migration/track-translations.md) | --- version: "v4" language: "en" --- # Manage Variants and Conditional Content This article compares how Scroll Versions and Scroll Content Manager handle variants and conditional content. We'll walk through what these features are and how each app supports them. **Scroll Documents** has been rebranded to **Scroll Content Manager**. Although the Loom video refers to the original name, all features shown in the video remain available. ## Variant Management Scroll Versions offers built-in variant management. You use *attributes* and *attribute values* to define which pages belong to specific variants. This provides fine-grained control over what content is shown to different audiences. Scroll Content Manager offers two approaches: * Basic variant support-- Built into the app, enabling you to test and set up two variants per document. * [Variants for Scroll Content Manager](https://marketplace.atlassian.com/apps/1226295/variants-for-scroll-documents?hosting=cloud&tab=overview)(Extension app) -- Unlocks advanced variant management features. Instead of attributes, Scroll Content Manager uses standard Confluence page labels to define which pages belong to which variant. This simpler setup makes it more accessible for teams unfamiliar with complex configuration. To learn more about variant management in Scroll Content Manager, see: [Manage Variants](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-variants-overview&version=latest&variant=default) ## Conditional Content Both apps have conditional content macros, which let you show or hide content based on variant rules. For example, displaying a paragraph only for certain user roles or product tiers. When converting from Scroll Versions to Scroll Content Manager, your existing Conditional Content macros are automatically converted to Scroll Conditional Content macros. These rely on Confluence page labels to control visibility within variants. To learn more about this process, see: [Conversion with Conditional Content](https://migration.k15t.com/scroll-apps/migration/convert-with-conditional-content.md) ## Preview Variants and Conditional Content Scroll Versions and Scroll Content Manager offer different ways to preview your conditional content and articles before publishing. **In Scroll Versions:** * Variants are selected via the variant picker in the Scroll navigation bar. When a variant is selected, the page tree grays out pages that aren't part of that variant * Conditional content macros are highlighted differently depending on the variant selected, giving you visual feedback on what will appear in each variant. **In Scroll Content Manager:** * Use the [Content Manager](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-eap-content-manager&version=latest&variant=default) to see which pages are apart of your variant. * Use the [Variant Preview](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-help-preview-variants&version=latest&variant=default)available in the Scroll page details panel. See which variant(s) a page belongs to, and how conditional content appears for each one before publishing or exporting. --- version: "v4" language: "en" --- # Manage Versions This article compares the version management features of Scroll Versions and Scroll Content Manager, focusing on how they handle versioning, inheritance, and page hierarchy. **Scroll Documents** has been rebranded to **Scroll Content Manager**. Although the Loom video refers to the original name, all features shown in the video remain available. ## Versioning Both apps help you manage multiple versions of your documentation, but they take different paths: * Scroll Versions uses space versions, meaning any changes you make affect the entire space. When working in Confluence, you first create the version, and then make changes in a specific version of your content. * Scroll Content Manager takes a different approach. You can define any page or page tree as a document, each with its own versions. This means you can have multiple documents within the same space, each with its own versioning scheme. The versioning approach in Scroll Content Manager also follows a baselining approach, meaning you work on your content first, and at any given point you can save a version of that content. ![Graphic comparing space structures. A Scroll Versions space shows Master and Change pages, while a Scroll Content Manager space displays a Working version tree alongside saved version trees.](https://migration.k15t.com/__attachments/a_799e94d837d78e3ed3db33ef497399f6b8239f7ef351467d3d591ecf452aaa5b/scroll-versions-and-scroll-content-manager-page-tree-comparison.png?cb=9dce6226f4ca42beccc18cda8dfcda02) Hierarchy of versions in Scroll Versions (left) and Scroll Content Manager (right) ### Access versions Accessing versions are similar, but with some key differences: * In Scroll Versions, the version picker appear in a Scroll navigation bar. Selecting a version updates the Confluence page view accordingly. * In Scroll Content Manager, the picker is found in the Document toolbox and redirects you to the relevant version. ## Inheritance and Versioned pages Let's explore the concepts of content inheritance and versioned pages. In Scroll Versions: * Pages are either versioned or unversioned. * Versioned pages start by inheriting content from the version in which they were created. * Once edited in a later version inheritance breaks, the page content is now version-specific. * Unversioned pages remain unchanged across all versions. In Scroll Content Manager: * There's no versioned/unversioned concept. Instead: * You work in a Working version (the latest draft). * When you save a version, Scroll Content Manager copies the page tree. * Each version is independent, changes in one version donot affect others. Scroll Content Manager gives you full control over your content, while it doesn't use automatic inheritance, you can easily copy and apply changes from one version to another whenever needed. For more information see: [Overwrite Page Content Between Versions](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-overwrite-page-content-between-versions&version=latest&variant=default) ## Page Hierarchy When it comes to hierarchy, here are the key differences between the two apps: * Scroll Versions uses master pages to organize content. All versions share the same page hierarchy, individual hierarchies per version are not supported. * Scroll Content Managermaintains theoriginal Confluence page structure**.** Each version can have its own unique hierarchy, offering greater flexibility. --- version: "v4" language: "en" --- # Manage Manual and External Translations This article shows how translation management works in Scroll Content Manager compared to Scroll Translations. **Use cases** Scroll Content Manager and its extensions are currently optimized for the following use cases: * [Product documentation](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) * [Modular product manuals](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-manage-modular-product-manuals&version=latest&variant=default) * [Internal knowledge bases and manuals in Confluence](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-manage-company-guides-manuals-and-handbooks&version=latest&variant=default) * [Process documentation](https://help.k15t.com/scroll-docs/?contextKey=create-and-manage-process-documentation&version=latest&variant=default) If you feel the app lacks features to help support your use case, don't hesitate to reach out to our team for feedback: [help@k15t.com](mailto:help@k15t.com) ## Internal and External Translation In both Scroll Translations and Scroll Content Manager, you have the option to translate content either internally or externally. Let's clarify these two options: * **Translate internally in Confluence**: In this method, a translator works directly within the Confluence editor to translate content. The key difference when transitioning to Scroll Content Manager is the editor interface. Unlike Scroll Translations, which has a split editor that displays the original language on the left and the translation on the right, Scroll Content Manager uses Confluence's own editor, which is more reliable. The source language content is directly copied into the editor for translation. * **Translate externally with XLIFF exports**: With this approach, content in the source language is exported into XLIFF format and sent to an external translator for translation. Once the translation is complete, it's imported back into Confluence. **Important to note** When translating externally in Scroll Content Manager, you can only export XLIFF files for translation. If you were exporting your languages to XML previously, don't hesitate to reach out to our support team: [help@k15t.com](mailto:help@k15t.com) While the translation options remain consistent between both apps, there will be differences in the translation workflow. These differences are outlined in the following articles * [Manual Translations: Scroll Translations vs Scroll Content Manager](https://migration.k15t.com/scroll-apps/migration/manual-translations-scroll-translations-vs-scroll-content-manager.md) * [External Translations: Scroll Translations vs Scroll Content Manager](https://migration.k15t.com/scroll-apps/migration/external-translations-scroll-translations-vs-scroll-content-manager.md) --- version: "v4" language: "en" --- # Manual Translations: Scroll Translations vs Scroll Content Manager If you're moving from Scroll Translations toScroll Content Manager*,* it's important to understand how manual translation workflows differ between the two. This article compares how content is translated manually within Confluence in each app and guides you through the new processes introduced by Scroll Content Manager. ## Manual Translation with Scroll Translations If you're currently using Scroll Translations (and possibly Scroll Versions), your typical workflow for manual translation looks like this: 1. Content is authored in the default (authoring) language. 2. Translators consult the *Translations Report* to identify pages needing translation or updates. 3. Translators manually translate each page using the translation editor, which displays the source and target language side-by-side. 4. Translated content is saved directly in the editor. 5. Users switch between languages using the language picker. This process will change slightly when moving to Scroll Content Manager, which also introduces versioning as a concept. ## Manual Translation with Scroll Content Manager With Scroll Content Manager and its extension app Translations for Scroll Content Manager, manual translation still happens within Confluence, but the workflow introduces the concept of versions: * **Working version**: The continuously evolving draft of your documentation. Ideally, this is where you add all new or updated content that hasn't been released yet. * **Saved versions** : Once the *Working version* is reviewed and approved, it can be saved as a new version. The saved version retains the content in the authoring language, enabling you to translate it into secondary languages. * **Language page trees**: Each language has its own set of pages under a version, enabling you to make independent changes to each version and translation. ### What if I don't want to version my content? While the recommended workflow in Scroll Content Manager is to: * Maintain the*Working version* in your defined authoring language, * save a version when content is ready, and * add or reuse translations in the saved version, you're not required to follow this process if versioning isn't relevant to your use case. For example, if you're managing a multilingual intranet or other continuously updated content without the need for version history, you can add translations directly to the *Working version* and choose not to save any versions. ## Manual Translation Workflows in Scroll Content Manager Scroll Content Manager supports two main manual translation workflows depending on whether you're working with multiple versions or only the *Working version*. ### Manual translation with multiple versions Use this approach if you version your documentation and want to translate each released version. Workflow: 1. Add new content to the *Working version*, which uses only the defined authoring language. 2. Review the content in the *Working version* before saving the version. 3. Save the *Working version* once it's ready, which creates a new version containing the defined authoring language. 4. Add translations to the new version. 5. Translate the pages manually within the dedicated page tree. 6. The process then starts over, if you have translated previous versions you'll also have the option to [reuse translated content](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-reuse-translations&version=latest&variant=default). ### Manual translation in the Working version only Ideal for teams who don't require saved versions. Workflow: 1. Add new content to the *Working version* in the specified authoring language. 2. Review the content in the authoring language. 3. If not added already, add the translations to the *Working version*. 4. Translate the pages manually within the dedicated page trees of each language. 5. The process starts over when you add new content to the authoring language and you [update your existing translations](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-update-translation&version=latest&variant=default). --- version: "v4" language: "en" --- # Migrate Variants to Scroll Documents - Sep'21 Welcome back to K15t's Cloud Migration News! This article is all about the release of [Variants for Scroll Documents](https://marketplace.atlassian.com/apps/1226295/variants-for-scroll-documents?tab=overview&hosting=cloud), complete with variant migration and integrations with Scroll Apps. ## Variants for Scroll Documents - The New App(roach) "Variants are like different flavors of your documentation" is a colorful description of the purpose of conditional content and variants and we're happy to bring these flavors to Confluence Cloud (and Data Center) with our newly released [Variants for Scroll Documents](https://marketplace.atlassian.com/apps/1226295/variants-for-scroll-documents?tab=overview&hosting=cloud) app. While most of our users know variants as a Scroll Versions feature, let's explore what's different in Scroll Documents. ### Labels Are The New Attributes As we were adapting the variant feature to work well in Confluence Cloud, we decided to drop attributes as we had them in Scroll Versions and use labels instead: both for pages and for paragraph-level conditional content macros. Instead, we created a powerful tool for defining variants rules: ![define-variants-rules.png](https://migration.k15t.com/__attachments/a_20da3dbfd205b75beae2f26cc6dbb816d516cbea453ff8fca2bb4dd6c0016fbf/define-variants-rules.png?cb=5b45d1c0c7592188796fc42203ee4149) Confluence users are more comfortable using page labels that any newly introduces concept and the new option to add labels to all child pages (see the tip above). ### A Modular Scroll App Suite Another notable change from what users know from Scroll Versions is that Variants for Scroll Documents is a separate app that functions as an extension for Scroll Documents, but has its own Marketplace listing and license. This is a new direction we're planning to explore with our apps that hopefully will help our users to only license and use the features they need for their particular documentation setup. Stay tuned for more news on this modular approach in the future! ## Migrate Variants from Scroll Versions to Scroll Documents In our efforts to enable every Scroll Apps user's migration to Confluence Cloud, developing a new feature is only half the battle -- migration is the other half. [Scroll Versions' migration tool](https://migration.k15t.com/scroll-apps/migration/open-cloud-migration-path-for-scroll-versions-user.md) has opened the migration by enabling users to create a Scroll Document that resembled their versioned space. Scroll Versions 4.1 introduces support for the migration of versioned spaces with variants: ![variant-migration-ui.png](https://migration.k15t.com/__attachments/a_cf6a05a0f6a7c1272cd5550aec5fe36a933eb948d5514571ed31eb693e836716/variant-migration-ui.png?cb=3a8836c5ad963b702145048ddcf22034) While the migration is rather straightforward, here are some points current Scroll Versions variants users should be aware of: * **Simple label rules**: Migrated variants are defined with a single rule and label, which the user can customize in the migration wizard as seen in the above screenshot. This label is applied to all pages and conditional content macros that are part of the variant. * **Block conditional content**: Unlike on Server, inline or word-level conditional content isn't available. In order to work around this restriction, the migration converts these to paragraph-level block macros. Just make sure to check pages that use inline conditional content after the migration. ## Atlassian Cloud \& Migration News * [**Scroll Viewport SAML beta**](https://help-cloud.k15t.com/scroll-viewport/13870596112.html): Access control for Viewport sites prepares to go to the next level by supporting authentication providers using SAML. If you're interested, please [reach out to our support team](https://support.k15t.com/tech-support). * **Variant support in Scroll Exporters**: Scroll Word and PDF Exporter now support the Variants feature in Scroll Documents, enabling users to create document exports of different variants. * **Feedback for Viewport sites** : The new integration with [Hyvor Talk](https://talk.hyvor.com/) allows users to collect feedback and comments for their documentation. [Check out our docs to learn more](https://help-cloud.k15t.com/scroll-viewport/Article-Feedback-Integration.13955399682.html) about how to integrate and make sure to use the 20% Hyvor Talk discount for Scroll Viewport users. ### Want to discuss your Cloud migration or sign up for the variants beta? Our support team is happy to help! [Get Migration Support](https://support.k15t.com/conversion-scroll-documents) --- version: "v4" language: "en" --- # Conversion and Migration Knowledge Base Have any lingering questions that you couldn't find answers to? Perhaps you'll discover them here: * [Scroll Versions and Scroll Translations for Confluence Cloud](https://migration.k15t.com/scroll-apps/migration/scroll-versions-and-scroll-translations-for-conflu.md) * [GDPR Compliance and Data Security](https://migration.k15t.com/scroll-apps/migration/gdpr-compliance-and-data-security.md) * [Licenses for Migration](https://migration.k15t.com/scroll-apps/migration/licenses-for-migration.md) * [Data Center Support for K15t Apps](https://migration.k15t.com/scroll-apps/migration/data-center-support-for-k15t-apps.md) * [Workflow Statuses After Conversion](https://migration.k15t.com/scroll-apps/migration/workflow-statuses-after-conversion.md) * [How to Keep the Old Space Key after Converting to Scroll Documents](https://migration.k15t.com/scroll-apps/migration/how-to-keep-the-old-space-key-after-migration-to-1.md) * [Dealing With External Links After Conversion](https://migration.k15t.com/scroll-apps/migration/dealing-with-external-links-after-conversion.md) --- version: "v4" language: "en" --- # Migration of Incoming Links When converting from Scroll Versions or Scroll Translations to Scroll Content Manager, one of the challenges you might face is handling incoming links from other spaces in your Confluence system. During the conversion process, you have the option to rewrite these links so they point to the corresponding pages in the new Scroll Content Manager-managed space. ## What are Incoming Links? Incoming links are page links from other spaces in your Confluence system that lead to pages within your Scroll Versions or Scroll Translations-managed space. During conversion, you can choose to update these links to point to the new Scroll Content Manager-managed space instead. This ensures that users navigating your Confluence system are directed to the corresponding pages in the new Scroll Content Manager managed space. Please note that the migrate links option is only capable of rewriting dynamic page links. Dynamic links are created using Confluence's built-in Link feature and direct to other pages within the Confluence system. They differ from static web links, which continue to point to the configured URLs. ## Why Migrate Incoming Links? Before deciding to migrate incoming links, it's important to assess their volume and significance. The [Migration Report](https://migration.k15t.com/scroll-apps/migration/run-the-migration-report.md)can help you identify spaces with a high number of incoming links to your managed space. If incoming links are a crucial part of your system's functionality, migrating them can: * Avoid broken links or user confusion. * Ensure consistency across your Confluence system. ## Key Considerations ### Permanent action Migrating incoming links is a permanent action and cannot be undone. Once the links are rewritten, they will permanently point to the new Scroll Content Manager-managed space. Make sure this step aligns with your migration strategy before proceeding. ### Backup recommendation Before performing this action, it's strongly recommended to back up your Confluence system. This backup serves as a safeguard in case you decide to revert any part of your migration process. ### Log reference After the migration is complete, the Confluence logs will provide a list of the page IDs where links were rewritten. This information can be useful for tracking and verifying the changes. ## How It Works This is how your should proceed if thinking about migrating incoming links: 1. **Analyze incoming links:** Use the [Migration Report](https://migration.k15t.com/scroll-apps/migration/run-the-migration-report.md) to identify the volume of incoming links to the Scroll Versions or Scroll Translations-managed space. 2. **Decide to migrate:** Determine if migrating the links aligns with your migration goals. 3. **Perform the migration:** Initiate the link rewrite process after the new Scroll Content Manager-managed space has been created. This will update all dynamic page links to redirect to the corresponding pages in the new Scroll Content Manager-managed space. 4. **Verify changes:** Review the Confluence logs to confirm the page IDs where links were rewritten. --- version: "v4" language: "en" --- # Conversion Options The Scroll Content Manager conversion tool offers a number of conversion options in addition to the general content selection based on versions, variants or languages. This article will teach you about these options and how they affect conversion results. Depending on the features enabled in your Scroll Versions or Scroll Translations managed spaces, the available conversion options may vary. ## Copy Space Permissions When you generate a space with Scroll Content Manager, it's only visible to you, the converting user. This gives you a private playground to test the conversion tool without other Confluence users peeking in. If you want to change that, you can check the "Copy Space Permissions" option. This means the generated space will inherit all the same permissions as the original space managed by Scroll Versions or Translations. It's a handy option if you want to maintain your existing access settings. Initially, avoid copying space permissions for early tests to keep the space private. However, during the actual conversion, we recommend enabling this option. If not, you'll have to set permissions manually afterward. ## Resolve Include Macros When converting to Scroll Content Manager, you'll encounter two conversion options: 1. "Resolve (Excerpt) Include macros in the Working version." 2. "Resolve (Excerpt) Include macros across all saved versions." We recommend sticking to the default setting, which entails: * **Not selecting** "Resolve (Excerpt) Include macros in the Working version." * **Selecting** "Resolve (Excerpt) Include macros across all saved versions." ![The resolve inclusions dialog during conversion, showing options to resolve include macros in the working version, saved versions, or both.](https://migration.k15t.com/__attachments/a_99ac9ebf1148aacfec8ec5a1ec7ed926aea083666d5f6f5f898a8c84eb983698/resolve-include-during-migration.png?cb=b8800970df4e25528109aa921aa20a95) By following these settings, your reused page tree will be positioned outside of the Working version of your Scroll documents, maintaining content reuse through Include macros. Meanwhile, Include macros in the saved versions will be resolved, ensuring that the content on those pages remains static and removing the macros themselves. ## Migrate "No Documentation" Content Do you have any content in your space that you don't want to have as a part of your versioned or translated documentation? This could be things like reports or management pages, which you still want to move over to the new Scroll Content Manager-managed space. Typically, these pages are located at the top level, above the root page of your documentation, and are not versioned. In Scroll Content Manager, by default, these pages will be moved to the Working version in your new Scroll Content Manager- managed space. However, if you want these pages to be added to all versions of your document, you can select the option: * "Migrate 'vsndoc-no-documentation' labeled page trees to all saved versions." ![Conversion dialog showing the option to migrate pages with the vsndoc-no-documentation label to all versions.](https://migration.k15t.com/__attachments/a_92f6d4442d84f255c421560c208a96b2cbca36ea94309574ac49498e7d29edf1/migrate-pages-with-vsndoc-label.png?cb=edab1dac311ae14d2ddf91036e371247) We recommend keeping this option unselected, which will convert the content to the Working version of your new Scroll document. Then, if they are not part of your versioned or translated documentation, place these pages above the root page of your Working version when you're done. ## Copy Restrictions for Working Version If you have configured version restrictions in Scroll Versions, this option allows you to automatically migrate them to your new Scroll document. These restrictions will be added to your new Working version. The user who executes the conversion process will automatically be granted permissions to the document. ![Conversion dialog with an arrow highlighting the option to copy version restrictions to the Working version.](https://migration.k15t.com/__attachments/a_6104d8f6c61fe45dfc8e478b225d01941136cbc1a090d0c7c3bfec58ea645a9f/copy-restrictions-to-working-version.png?cb=5c777f41ff684eb8527bac4a06165758) ## Copy Restrictions for Saved Versions If you have set version restrictions in Scroll Versions, this option allows you to convert restrictions to your new Scroll document automatically. The restrictions will be copied only for the versions that you chose to be converted (excluding the version you selected to be the Working version). The user who executes the conversion process will automatically be granted permissions to the document. ![Conversion dialog with an arrow highlighting the option to copy version restrictions to saved versions.](https://migration.k15t.com/__attachments/a_dd8aaec3457159224949dd31fdae57aa763145a3367d00db8e79d015f9c9d8d8/copy-version-restrictions-to-saved-versions.png?cb=3da5445fb18c08090045898d6545a2f4) ## Copy Inline Comments This option is enabled by default, meaning all inline comments from your original content will be included in the converted Scroll document. To prevent duplicated inline comments across multiple versions, avoid checking this option during conversion. ## Convert Page Keys Also enabled by default, this option ensures that any page keys assigned in Scroll Versions are converted to [Context Keys](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-help-context-keys&version=latest&variant=default) in Scroll Content Manager. While page keys and context keys serve a similar purpose (generate stable links), there's one key difference: Context Keys can be used in Scroll Sites, but not within the native Confluence UI. ## Copy Blog Posts This option is enabled by default. When selected, your blog posts will be converted in the following way: * Only the last revision is copied * Creator und creation date are kept * Last modification date → set to the date of conversion * Last modifier → set to the user who started the conversion * Page links are not converted ## Next Steps Now that you understand the conversion options, you can convert your documentation to Scroll Content Manager. Make sure to check and change the settings as needed before starting. Also, try a small test first to ensure it meets your needs. Once you're happy with the settings, you can convert your documentation and start using Scroll Content Manager to manage your content. Head back to [Convert a Space to Scroll Content Manager](https://migration.k15t.com/scroll-apps/migration/convert-a-space-to-scroll-documents.md) to follow the last steps in your conversion journey. Happy converting! --- version: "v4" language: "en" --- # New Feature: Enhanced Migration Report for Scroll Managed Spaces - Aug '23 Attention all Scroll Versions and Scroll Translations users! We are pleased to introduce an improved Migration Report with the version 4.5.2 release. This update brings greater readability and a new global admin UI, making it easier for Confluence Administrators to access the report. ## What is the Migration Report? The [migration report](https://migration.k15t.com/scroll-apps/migration/run-the-migration-report.md) is here to help your team identify spaces that need to be converted to Scroll Documents during your migration to Confluence Cloud or Scroll Documents on Data Center. The primary goal of this new feature is to provide you with a comprehensive overview of all your spaces that need to be converted to Scroll Documents as part of your migration journey. You can see how Scroll Versions and Scroll Translations are being utilized across all spaces in your Confluence system, providing a solid foundation for planning your conversion to Scroll Documents. ### How can you benefit from the new Migration Report? Whether you're moving to Confluence Cloud or Scroll Documents on Data Center, the report offers valuable insights into how Scroll Versions and Scroll Translations are being utilized within your organization. To start using the Migration Report: 1. Update to the latest version of Scroll Versions and Scroll Translations. 2. Follow the links below to learn how to create and read the Migration Report. * [Create the report](https://migration.k15t.com/scroll-apps/migration/how-to-create-the-migration-report.md) * [Read the report](https://migration.k15t.com/scroll-apps/migration/run-the-migration-report.md) Please note that the analysis currently checks for Scroll Versions and Scroll Translations features exclusively. Other Scroll apps are not included in the report. **We are here to help you navigate the migration process smoothly.** Should you have any questions or need assistance interpreting the results, [Get Migration Support](https://k15t.jira.com/servicedesk/customer/portal/3/group/6/create/24) ### Looking ahead: Thank you for choosing Scroll Versions and Scroll Translations and we look forward to helping you embrace the benefits of Scroll Documents. In the meantime, explore the rest of K15t's Cloud Migration Hub where you'll find everything you need to know about our app availability, feature parity, migration paths, and our Cloud roadmap. [Check it out →](https://migration.k15t.com/migrate-to-cloud/) --- version: "v4" language: "en" --- # Open Cloud Migration Path for Scroll Versions Users - May'21 This month's update is all about the latest releases of Scroll Documents, Scroll Versions, and Confluence Cloud Migration Assistant. Combined, these three open the very first Cloud migration path for Scroll Versions users. ## What Can Be Migrated The initial migration path enables migrating versioned spaces that aren't using variants or Scroll Translations to Scroll Documents on Confluence Cloud. If that applies to your content, then you're probably ready to migrate. Users whose content does use variants and translations unfortunately will have to migrate at a later point in time. Until then, feel free to check out the migration tool and [reach out](https://k15t.jira.com/servicedesk/customer/portal/3/group/5/create/24) if you have any feedback or questions. ## The Apps You'll Need To make sure you're well equipped to complete the migration, make sure the apps listed below are updated to these versions or higher: * [**Scroll Documents 3.0+**](https://marketplace.atlassian.com/apps/1217608/scroll-documents-for-confluence?hosting=server&tab=overview) introduces a new internal data model that supports the migration from Scroll Versions. * [**Scroll Versions 4.0+**](https://marketplace.atlassian.com/apps/1210818/scroll-versions-for-confluence?hosting=server&tab=overview) introduces the Migration Tool, capable of generating versioned Scroll Documents from versioned spaces. * [**Confluence Cloud Migration Assistant 3.2+**](https://marketplace.atlassian.com/apps/1219672/confluence-cloud-migration-assistant?hosting=server&tab=overview) rolled out a bug fix which is crucial for migrating Scroll Documents. ## The Cloud Migration Path Explained The Cloud migration path is a two-step process visualized in the diagram below. ![image-20210528-121946.png](https://migration.k15t.com/__attachments/a_fd54d490c4e61d912d5bd80e1c1952fdf1c0ecb246bf4379f57b3929f75222c7/image-20210528-121946.png?cb=a3ba2b132d3970cde548dc7fa87c4bd3) ### Step 1: From Scroll Versions to Scroll Documents The first step happens within your Server instance of Confluence and utilizes the Scroll Versions Migration Tool. The migration is initiated separately for each space and does not alter your versioned space in any way. Instead, Scroll Versions creates a new space containing a Scroll Document with same versions, content and comments as your versioned space. For more details on the Scroll Versions to Scroll Documents migration, check out the [Scroll Versions migration path documentation](https://migration.k15t.com/scroll-apps/migration/the-conversion-path.md). ### Step 2: From Server to Cloud The second step of the migration utilizes the automated migration provided by Atlassian's [Confluence Cloud Migration Assistant](https://marketplace.atlassian.com/apps/1219672/confluence-cloud-migration-assistant?hosting=server&tab=overview) (CMA). Starting with its 3.2.0 release, the CMA is able to migrate spaces containing Scroll Documents without any manual action required. The mentioned change in the CMA is still **behind a feature flag** . Make sure to check out [Scroll Documents' migration path documentation](https://help.k15t.com/scroll-docs?contextKey=migrate-to-cloud&version=latest&variant=default) before starting the Cloud migration. ## What's Next? Going forward, our plan is to add more content management features known from Scroll Versions into Scroll Documents and to provide migration support for these feature within the migration tool: * **Phase 1** : Versions done * **Phase 2** : Variants in progress * **Phase 3** : Translations open Smaller improvements to the migration and new minor features in Scroll Documents will be shipped in between these phases. ## Atlassian Cloud \& Migration News * [**Authentication in Scroll Viewport Cloud**](https://help-cloud.k15t.com/scroll-viewport/Set-Up-Authenticated-Access.1381629960.html) was one of the highly anticipated features as it allows users to create Viewport sites with controlled access. This feature has now been released and opens the migration path for users publishing their content to an access-restricted help center. * [**Redirects in Scroll Viewport Cloud**](https://help-cloud.k15t.com/scroll-viewport/Manage-Redirects.1464434689.html) allow users to have more control over pages and their URLs in their Help Center. For migrating users who keep their domain name, this feature is a great tool to make sure all of your previously shared links remain functional after migration. ### Want to discuss your Cloud migration? Our support team is happy to help! [Get Migration Support](https://k15t.jira.com/servicedesk/customer/portal/3/group/5/create/24) --- version: "v4" language: "en" --- # "Page ABC gets a new page title 'ABC1' due to conflict with another page" ## Symptom While converting a Scroll Versions managed space from Scroll Versions to Scroll Content Manager, you encounter the following warning: > "Page ABC gets a new page title 'ABC1' due to conflict with another page" ## Explanation When using duplicate page titles in Scroll Content Manager a number has to be appended to duplicate titles as this feature is not available in Scroll Content Manager. ## Resolution The warning message is just a notification to inform you that the page title has been altered. Hence, no resolution is required. However, if you wish, you can navigate to the page specified in the warning within the converted space and manually modify the page title. --- version: "v4" language: "en" --- # "Page ABC references an attachment XYZ whose data cannot be found" ## Symptom While converting a Scroll Versions managed space from Scroll Versions to Scroll Content Manager, you encounter the following warning: > "Page ABC references an attachment XYZwhose data cannot be found" ## Explanation The mentioned attachment is likely broken, as the data cannot be accessed. ## Resolution To resolve the problem, follow these steps: 1. Go to the page referenced in the error message. 2. Click on the page tools icon for the page (•••) and choose **Attachments**. 3. Find the attachment specified in the error message. 4. Remove the attachment. 5. (Optional) Add the attachment again if it's not corrupted. 6. Attempt to convert the space again. If the issue persists, [contact support](https://k15t.jira.com/servicedesk/customer/portal/3)for further assistance. --- version: "v4" language: "en" --- # Prepare Welcome to the preparation phase of your Scroll Content Manager conversion journey! If you've reached this stage, you've already assessed your readiness to convert to Scroll Content Manager and decided that now is the right time to proceed. During this preparation phase, your primary focus will be to prepare yourself and your Confluence spaces for the actual conversion to Scroll Content Manager. This involves several key steps: 1. **Use migration insights**: Leverage the migration report to identify which spaces are ready for conversion. 2. **Clean up spaces**: Determine what content is worth keeping, and organize your spaces accordingly. 3. **Address potential blockers**: Resolve any blockers or warnings that may delay your conversion. 4. **Replace unsupported macros:**Some Scroll macros have to be replaced with their Confluence native counterpart before conversion. This preparation phase is crucial for a successful conversion experience. By following these steps, you'll be well-equipped to make a seamless and efficient transition to Scroll Content Manager. ## The Goal of This Phase Your goal in this phase is to ensure that all relevant spaces are well-prepared for a successful conversion to Scroll Content Manager. To help you achieve this goal, we recommend the following actions: * **Read the articles**: Dive into the articles in this section to learn best practices for preparing your spaces for Scroll Content Manager. You'll learn what to keep in mind before and during the conversion process. * **Prepare the spaces**: Run health checks, apply the best practices, and leverage the knowledge you've gained from the articles and the migration report to ensure your spaces are in optimal condition to convert. * **Conduct a test conversion**: Prior to the official conversion, perform a final test conversion to ensure a smooth transition. This step is essential, especially if you have an approaching deadline. ## Next Steps Before preparing your spaces and conducting your last test conversion, start by reading these articles: * [Decide What to Keep -- Streamlining Your Content](https://migration.k15t.com/scroll-apps/migration/decide-what-to-keep.md) * [Preparing Multiple Top-Level Pages](https://migration.k15t.com/scroll-apps/migration/preparing-multiple-top-level-pages.md) * [Categorize the Pages](https://migration.k15t.com/scroll-apps/migration/categorize-the-pages.md) * [Run an Initial Scroll Health Check](https://migration.k15t.com/scroll-apps/migration/run-a-first-scroll-health-check.md) * [Fulfill the Conversion Requirements](https://migration.k15t.com/scroll-apps/migration/fulfil-the-conversion-requirements.md) * [Effective Best Practices using the Space Migration Report](https://migration.k15t.com/scroll-apps/migration/effective-best-practices-using-the-space-migration.md) * [Replace (Excerpt) Include+ macros](https://migration.k15t.com/scroll-apps/migration/replace-excerpt-include-macros.md) --- version: "v4" language: "en" --- # Prepare for Your Migration to Scroll Documents - May'23 If you are a user of Scroll Versions or Scroll Translations, you might be familiar with our recommendation to [consider a migration](https://help-cloud.k15t.com/scroll-versions/4.4/migration-path) to their new generation successor [Scroll Documents](https://marketplace.atlassian.com/apps/1217608/scroll-documents-for-confluence?hosting=cloud&tab=overview). When preparing for this migration, we recommend making use of the new migration report. We've just given the report a big overhaul and have added detailed documentation how to work with it. To learn more about the report and how to use it see: * [Migration Report](https://help-cloud.k15t.com/scroll-versions/4.5/migration-report) * [How to Create the Migration Report](https://help-cloud.k15t.com/scroll-versions/4.5/how-to-create-the-migration-report) ## Why Use the Migration Report? To achieve a successful migration preparation is key. You can run the report in your Confluence system to get information about all spaces which are using Scroll Versions or Scroll Translations. The purpose of the report is to help you get an idea of which features of Scroll Versions or Scroll Translations you are using, and how they are supported in Scroll Documents. If the necessary feature support has not yet been implemented, this could be a good indication that you should wait with migration and[reach out to our support](https://support.k15t.com/tech-support). ### Want to discuss your Cloud migration? Our support team is happy to help! [Get Migration Support](https://support.k15t.com/tech-support) --- version: "v4" language: "en" --- # Preparing Multiple Top-Level Pages If your space contains multiple top-level pages, you can decide before the conversion how they should be treated in the Scroll Content Manager space. Depending on the purpose of your top-level pages, you can choose one of the following approaches: ## OPTION 1: If You Want to Include Top-Level Pages If your top-level pages are regular content pages that should be included in your document for publishing and versioning, no action is required before the conversion. They will automatically become part of the document structure. ## OPTION 2: If You Want to Exclude Top-Level Pages If your top-level pages function as an include library or some internal pages (for example, task lists), you may want to exclude them from the document and keep them unversioned. In this case, you can apply labels before the conversion to define their location in the page tree that will be created during the conversion. For more information about how to use labels, refer to the [labeling documentation.](https://migration.k15t.com/scroll-apps/migration/categorize-the-pages.md) ## Example A source space has the following page tree, where include library and task list are unversioned pages. ![image-20260224-080038.png](https://migration.k15t.com/__attachments/a_0ecf605ff599daf0fa775926dd5926b3aef2dee01fff1ff21462361291e97491/image-20260224-080038.png?cb=f5cf638f294a71f7ac47eb3a2c46ab51) Page tree in Scroll Versions enabled space ### Option 1: Include Top-Level Pages When converting this space to Scroll Content Manager as it is, all pages will become part of the document (called "Product documentation" in this example) for publishing and versioning. ![image-20260224-082929.png](https://migration.k15t.com/__attachments/a_8412c8bd62cbfb72b08aec9cab12697835d1f2af441c7339565f50e904b6de9f/image-20260224-082929.png?cb=dfd00ce1437fdd3b8bf15d48b8b63084) Whole page hierarchy is included to the created document ### Option 2: Exclude Top-Level Pages Before converting this example space to Scroll Content Manager, we label the other top level pages the following way: * Using label *vsndoc-include-library* for "Include library" pages * Using label *vsndoc-no-documentation* for the "Task list" page. As a result only the main documentation is part of the document called "Product documentation". Task list and include library pages are not part of the document and won't be included in publishing or versioning. ![image-20260224-081903.png](https://migration.k15t.com/__attachments/a_05b1a37c822a1ae0abb085c184845ddeaf73263751f14b87310710174a015f3d/image-20260224-081903.png?cb=8bd50cb75a1d4ac94bb0b9287fa98577) Only the main documentation page hierarchy is included to the created document --- version: "v4" language: "en" --- # Publish Translations This article outlines how publishing options differ when moving from Scroll Translations (and Scroll Versions) to Scroll Content Manager and its extension apps. **Use cases** Scroll Content Manager and its extensions are optimized for: * [Product documentation](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-publish-product-documentation&version=latest&variant=default) * [Modular product documentation](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-manage-modular-product-manuals&version=latest&variant=default) * [Internal knowledge bases and manuals in Confluence](https://help.k15t.com/scroll-docs/?contextKey=k15t-docs-create-and-manage-company-guides-manuals-and-handbooks&version=latest&variant=default) * [Project and process documentation](https://help.k15t.com/scroll-docs/?contextKey=create-and-manage-process-documentation&version=latest&variant=default) If your use case isn't fully supported, feel free to contact us at: [help@k15t.com](mailto:help@k15t.com) ## Publishing Options with Scroll Translations With Scroll Translations, you can publish content in multiple ways: * **Online help center:**Use Scroll Sites to deliver content to an internal or public site, on its own or with Scroll Versions. * **Offline manuals:**Export content to PDF, Word, or HTML using the Scroll Exporter apps. * **Multilingual intranet:**Publish translated content to a new space or manage it within a Scroll Translations-enabled space. ## Publishing Options with Scroll Content Manager Scroll Content Manager supports similar publishing workflows for translated content: * **Online help center:**Use Scroll Sites to create a user-friendly, multilingual help center with language picker support. * **Offline manuals:**Export translated documents to PDF, Word, or HTML using Scroll Exporters. * **Multilingual intranet:**Publish translations within Confluence to a separate target space, or keep all translations directly within the authoring space. ## Key Differences for Multilingual Intranets in Scroll Content Manager If you're converting from Scroll Translations to Scroll Content Manager for a multilingual intranet, here are the key changes to be aware of. ### Publishing to another space When publishing languages to another target space with Scroll Content Manager, keep the following changes in mind: * **Single-language publishing**: Only one language can be published at a time to the same space. * **Prefixes required**: To publish multiple languages to the same target space, use prefixes to distinguish each language's page tree. * **No language picker**: In the target space, users navigate by selecting pages in the page tree, there's no language picker. For better navigation experience, publish each language to its own space. ### Publishing within the authoring space When keeping the languages within your authoring space with Scroll Content Manager, keep the following changes in mind: * **Separate page trees per language**: Each language gets its own structured page tree. * **Language picker available** : Readers can switch languages using the picker in the *Document toolbo*x. [Next Page](https://migration.k15t.com/llms-full.txt/1)