Dependencies

• You have a custom implementation using the legacy offer system you want to migrate from.
• You have a working Offers integration before migrating your legacy offers onto it. See Getting Started with In-Game Offers for details.

Overview

Offer Groups were added in R15, so if you're using an older version of the Metaplay SDK you might want to migrate your old offers over to benefit from the extra functionality that they provide. A possible path to do so could be along these lines:

• Using Metaplay's Offers, implement equivalent functionality to your existing offers. The two systems can still exist side-by-side at this point; or, if more convenient, the existing implementation can be gradually changed to use Metaplay's Offers.
• Remove actual functionality of the old implementation, leaving only enough code to be able to deserialize players' existing states related to the old offers.
• Implement code that populates an existing player's Metaplay Offer state based on the player's existing old offer state.
• Add a Schema Version Migration for player Entities, as described in Entity Schema Versions and Migrations, which invokes the code mentioned in the above bullet point.

Metaplay's Idler reference project contains an example of such migration code in LegacyShopOffer.cs. Idler previously had a simple shop offer implementation which was later migrated to Metaplay SDK's Offers.

That said, your use case may be more complex than Idler's, so this approach may need to be adjusted as necessary. Don't hesitate to contact us for support!