Knowledge Base Migrations to Vanilla - HL Vanilla Community
<main> <article class="userContent"> <p>The <strong>Vanilla Knowledge</strong> feature is the perfect complement to your Vanilla community because you can use it to host content right in your community. You can create your own knowledge bases and then populate them with <em>staff-written articles</em>, <em>converted community posts</em>, and migrated external content.</p><p>📝 <strong>NOTE</strong>: This article provides information on <strong>migrating content</strong> into an existing knowledge base (<strong>KB</strong>). If you want to create a KB, see <a href="https://success.vanillaforums.com/kb/articles/81" rel="nofollow noreferrer ugc">Vanilla Knowledge User Guide</a>.</p><h2 data-id="types-of-migrations">Types of migrations</h2><p>The Vanilla SuccessTeam offers knowledge base migrations for any Vanilla customer who wants to import existing KB content into Vanilla. There are three types of KB migrations:</p><ul><li><strong>Vanilla Forum Category to KB</strong>: If you're an existing customer who has been leveraging our Community platform to share knowledge, you probably have instructional posts under a dedicated category; you can convert these posts into articles in a knowledge base.</li><li><strong>External KB to Vanilla KB</strong>: If you have an existing KB hosted on another platform, you can migrate that KB into a knowledge base in Vanilla.</li><li><strong>New customer migration from external forum and KB</strong>: If you are new to Vanilla and have an existing KB hosted on another platform, you can migrate that KB into a knowledge base in Vanilla.</li></ul><p>Regardless of your use case, our professional services and Knowledge teams can build a porter package for you so that you can get started with your own Vanilla Knowledge KB.</p><h2 data-id="migration-process">Migration process</h2><p>We want to be sure that your migration of content into a Vanilla KB is successful, so we've established an effective migration process.</p><div class="embedExternal embedImage display-large float-none"> <div class="embedExternal-content"> <a class="embedImage-link" href="https://us.v-cdn.net/6030677/uploads/GBNYK3SM4CBE/migration-process-steps.png" rel="nofollow noreferrer noopener ugc" target="_blank"> <img class="embedImage-img" src="https://us.v-cdn.net/6030677/uploads/GBNYK3SM4CBE/migration-process-steps.png" alt="migration process steps.png" height="407" width="888" loading="lazy" data-display-size="large" data-float="none"></img></a> </div> </div> <h2 data-id="considerations">Considerations</h2><p>Each platform is unique, so as we enter the migration-estimate phase, there are a few things to keep in mind. Review the features below and provide any information where applicable.</p><h4 data-id="comments">Comments</h4><p>The Vanilla KB is currently not configured to house comments. Article comments and feedback are <strong>not</strong> migrated with the article.</p><h4 data-id="helpful-votes">Helpful votes</h4><p>We can migrate the data related to an article's reputation (i.e., it’s “helpful” rating); however, ratings might be measured differently on different platforms (e.g., "Yes or No" versus "Like"). Provide any information related to your article-rating system.</p><h4 data-id="localization">Localization</h4><p>If your current knowledge base supports multiple languages and you plan to migrate translations for your articles, specify the number of languages that you plan to support in your Vanilla KB.</p><h4 data-id="roles-and-permissions">Roles and permissions</h4><p>We can migrate <strong>user-role information</strong> but we cannot migrate permissions. Each platform manages permissions differently so there may not be a 1:1 match within Vanilla's Permissions framework. After we’ve imported the user roles, you can configure your permissions.</p><h4 data-id="iframes-and-embedded-content">iFrames and embedded content</h4><p>Does your existing KB include embedded content, such as YouTube videos related to the subject matter? Vanilla’s editor automatically embeds images and GIFs, as well as URLs from common sources (YouTube, Vimeo, Twitter, and Pinterest). Provide all available information about specific or custom types of embedded content that you want migrated.</p><h2 data-id="migration-estimate-checklist">Migration estimate checklist</h2><p>In addition to the above information, each migration estimate requires that some basic information and assets be shared with the Vanilla team.</p><p><strong>Database info</strong></p><p>The most important part of the migration is the data. We’ll need a full database export to complete the estimate.</p><p>📝 <strong>NOTE</strong>: In some cases, we may use the API for a migration; if this applies to your migration, provide your <strong>API docs</strong> and <strong>access token</strong> in addition to the following.</p><p> Provide:</p><ul><li>A link to your current knowledge base</li><li>Software name and version</li><li>Monthly pageviews (globally)</li><li>Number of articles</li><li>Are there attachments to be migrated?<ul><li>If yes: number of files AND total size</li></ul></li><li>A complete knowledge base database export, including:<ul><li>All Knowledges Bases</li><li>All Categories</li><li>All Articles</li><li>All User and User Data</li><li>All data linked to Helpful Votes</li></ul></li></ul><p><strong>Redirects</strong></p><p>Vanilla’s porter packages can also be configured to work with our Redirector plugin. If you would like us to implement redirects from your old content to the new, provide example URLs for the following (including any variations):</p><ul><li>Knowledge Bases</li><li>Categories</li><li>Articles</li><li>Profiles</li><li>Any other pages you wish to redirect</li></ul><p><strong>Other data</strong></p><p>There may be other data you wish to import into Vanilla. If there is anything you are curious about, your account executive or CSM will work with you.</p> </article> </main>