Migrating from Xsolla to Neon

This guide outlines the high-level migration steps from Xsolla to Neon. It assumes you already have a full Xsolla integration with your game, including:

• Authenticating players via player ID
• The game's backend grants purchases from the Xsolla webshop
• Inventory is managed in Xsolla via CSV or API

We’ll help you migrate smoothly—with scripts to convert your inventory and white-glove support throughout the process.

Step 1: Migrate authentication

Neon's preferred way of authenticating users is via the authentication API. We also support player ID login (likely what is already in your Xsolla shop) as a backup option to the API, and follows the same paradigm as you support today.

• Players input their player ID manually, and we use that player ID to determine offer segmentation.
• We also support validating these account IDs via the account.validate callback; you can provide data about the account (like display name) that we'll show the user to let them verify they've linked the correct account.
  • To enable this flow, register a listener for the account.validate callback, then let us know you're ready to turn on account validation.

We can work with you to enable this authentication method, and create images or videos that instruct users on where to find their account IDs.

Step 2: Update your inventory

Neon allows you to update your inventory via CSV (dashboard) or API. We have also had customers transform their existing Xsolla inventory spreadsheets to Neon tailored ones using a custom script we offer.

Additionally, Neon allows personalized offers in the storefront at the player's time of authentication. Neon offers an account inventory callback for your game to respond to with the offers, segmented for that specific user.

Step 3: Integrate with the Neon purchase and fulfillment flow

Much like your existing integration, Neon provides webhooks to your listeners to let you know when an item needs to be fulfilled in game (when purchases are completed). The webhook and corresponding API response follow similar terminology to Xsolla so there are no heavy re-mapping exercises required.