Business to Enterprise Migration

Overview

Stack Internal's flagship Enterprise product offers many advantages over the Free, Basic, and Business tiers. Stack Internal Enterprise leverages the power of AI with intelligent content ingestion, MCP server integration, AI-enhanced search, AI chat thread summaries, and more, Enterprise users also enjoy custom community privileges, additional customizations, webhooks, Visual Studio Code integration, and much more.

If your company currently uses Stack Internal Free, Basic, or Business tiers, you may want to migrate to Stack Internal Enterprise to take advantage of these additional benefits. If you do choose to upgrade to Enterprise, Stack Overflow has a complete migration plan based on real-world testing to get your data safely and securely moved to your new site.

Migration planning

We’ll work with you to identify the right configuration for your new hosted Enterprise site and work through the actual steps of the migration. The Stack Internal support team is ready to provide documentation, answer questions, or meet with your IT team.

Hosted Enterprise environment

Your Sales representative will reach out with the options we have available for hosting in our Azure environment. We can help you identify the appropriate level of hosting and select the options that will best serve your team going forward.

Customer requirements

Identity provider

Stack Internal Enterprise requires the use of an identity provider such as Okta or Microsoft Entra ID.

Even if you already use an identity provider for your current Stack Internal site, you'll need to engage your IT team to create a new single-sign-on application for the new site as it will have a different URL. The new SSO application will need to preserve the User and Email identifiers to correctly map user data.

Third-party integrations

Because Stack Internal Enterprise handles third-party integrations differently, the migration to Enterprise will require your IT team to reconfigure any existing integrations such as Slack, Microsoft Teams, or Github.

In addition to the documentation linked above, Stack Overflow is available to answer questions or join a call with your IT team during setup.

Email allowlist

Stack Overflow strongly encourages having your IT team add @stackenterprise.co to your email allowlist.

Migration details

Migration plan

1. Once you sign a contract, a member of the Sales Engineering team will reach out to gather configuration details for your Enterprise site. Once we have those details, we'll pass them to the support team for delivery.
2. The support team will create your new site and then work with you to set up Single Sign-On (SSO). We cannot perform the data migration until this is done.
3. Once an agreed-upon date for the migration arrives, your legacy site will become unavailable during the data migration. The process can take up to 48 hours.
4. We'll let you know when the migration is complete, at which point you’ll be free to start using your new Stack Internal Enterprise site.
5. When your new site is live, your legacy site will also become available again. We recommend limiting access to the legacy site and directing users to your new Enterprise site (no data will flow between them).
6. You'll need to enable and/or review the following admin settings:
   • Communities
   • Auto SME
   • MCP Server
   • Ingestion
   • Enhanced Search
   • Unified Search
7. We also suggest performing a data download on your legacy site.
8. As a last step we will decommission your legacy site at an agreed-upon date.

Known limitations

• The migration to Enterprise will not preserve your third-party integrations. Due to changes in URL structure and integration architecture on the Enterprise tier, you'll need to re-install all third-party integrations.
• API keys are not part of the migration process. If you have apps that use the API, you'll need to update them with a new API key.
• The migration will return your email preferences to their defaults. You'll need to set those again.
• The migration will not import deactivated users. If a deactivated user returns to your Stack Internal site, it will consider them a new user.
• You'll find certain features (such as Communities and Auto SME) disabled by default. Your data is still intact; you just need to re-enable these features.