nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Migration

Higher Logic Vanilla (Vanilla) offers full, professional migration services from nearly any other community platform. If you provide the data, we’ll figure out how to make it work in Vanilla.

NOTE: The process below assumes you will provide a database dump. We also perform API-based migrations from cloud services when that is necessary and possible. Talk to your account representative if you require a different type of migration like this.

Migration process overview

You provide the platform name, version number (if applicable), and the number of users and posts for your current community platform.
Vanilla will provide an SFTP drop.
You provide a test dump of your data to the SFTP. This is typically a database dump, but may include additional files like avatars or attachments depending on your platform. Please provide a full dump for an accurate estimate. Vanilla will generally accept an NDA if one is required.
You provide the email address for the individual who will become the owner account.
You provide any working username and password combination for testing.
Vanilla will evaluate the data and provide a cost estimate and, if requested, a downtime estimate (how long your community will need to be offline during the transition).
Vanilla will provide feedback on concerns, limitations, or other needs.

Test migration

Vanilla will import your test dump to a Vanilla community.
You review the test import and provide feedback on data integrity.
Vanilla makes any necessary corrections.
You provide a list of URL patterns that will need to be 301 redirected (discussions, profiles, categories, etc.). We will have a pre-existing list for most common platforms, but be sure to mention any customizations or special URLs you need us to handle.
Vanilla implements the 301 redirects and you test them.
A final migration is scheduled.

Final migration

You place your current community into read-only mode.
You create a fresh data dump, upload it to Vanilla’s SFTP, and notify your contact(s) at Vanilla.
Vanilla confirms it received your final dump and the final import begins.
Vanilla notifies you when the import is complete.
You verify the import is correct.
You switch over DNS, SSO, and/or any other final switchovers. Consult with your Vanilla contact if you are unsure.
If your community was previously on a domain not being redirected to your new community, be sure to 301-redirect the folder (with the entire URL intact) to your new community.

Migration security

Migration data should always be sent to Vanilla via SFTP, available by request to your Account Manager. Data can optionally be encrypted using Vanilla’s Public Key, provided below:

Personally-identifiable information

If a client does not wish to provide email addresses during a migration, we recommend formulating dummy email addresses. We can do this automatically during the import, if requested.

⭐️ EXAMPLE: {uniqueid}@yourdomain.com, where {uniqueid} is your equivalent of our UserID - a non-private, unique identifier for the user.

Most single sign-on services work by matching accounts based on email address. To work in this scenario, the authentication endpoint must construct (or have on record) an identical dummy email address. This allows the seamless authentication of the user against the correct account without using real personal info.

More information is available from our Privacy Policy and our developer documentation on data privacy.