> ## Documentation Index > Fetch the complete documentation index at: https://devdocs.xbox.com/llms.txt > Use this file to discover all available pages before exploring further. # Entities migration information > Move title, player, and character data from PlayFab account and data APIs to the entity API, including terminology and access pattern changes. The entity API introduces new access patterns that are designed to alleviate the pain points of the current account and data systems. The information presented here is useful if you previously used the following methods to implement data management for your Title, Player, or Character information. **Title** access: * client/[GetTitleData](xref:titleid.playfabapi.com.client.title-widedatamanagement.gettitledata) * admin/[GetTitleData](xref:titleid.playfabapi.com.admin.title-widedatamanagement.gettitledata) * server/[GetTitleData](xref:titleid.playfabapi.com.server.title-widedatamanagement.gettitledata) **Player** access: * client/[GetUserReadOnlyData](xref:titleid.playfabapi.com.client.playerdatamanagement.getuserreadonlydata) * client/[UpdateUserData](xref:titleid.playfabapi.com.client.playerdatamanagement.updateuserdata) * client/[UpdateUserPublisherData](xref:titleid.playfabapi.com.client.playerdatamanagement.updateuserpublisherdata) **Character** access: * client/[GetCharacterData](xref:titleid.playfabapi.com.client.characterdata.getcharacterdata) * client/[UpdateCharacterData](xref:titleid.playfabapi.com.client.characterdata.updatecharacterdata) Using the entities API, you can call a single method to save the data values for title, player, and character entity types. The API provides access rules that replicate and expand the current system behavior of custom data in a better interface. In some regards, these changes aren't backwards compatible. However, you can add calls to the entity API without changing the behavior of the existing APIs. ## Terminology The following table describes refinements in terminology related to the entity APIs. | Term | Description | | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **title** | This concept is unchanged. Your title may contain global information available to all players. This is similar to [TitleData](xref:titleid.playfabapi.com.client.title-widedatamanagement.gettitledata). It's identified by the title ID (`TitleId`) of the game/application. | | **master\_player\_account** | This entity type allows you to share information about a player across multiple games in a namespace. This is similar to [UserPublisherData](xref:titleid.playfabapi.com.client.playerdatamanagement.getuserpublisherdata). It's identified by the player ID (`PlayFabId`) of the player, which is returned as part of any login or any call to retrieve account information for the player account (for example, the PlayFab Client API [GetAccountInfo](xref:titleid.playfabapi.com.client.accountmanagement.getaccountinfo)). | | **title\_player\_account** | This concept is based on user/player in the existing API methods. Each player can contain some information for the current title. This is similar to the [GetUserData](xref:titleid.playfabapi.com.client.playerdatamanagement.getuserdata) method. This is identified by the entity ID (`EntityKey.Id`) you get back in the [EntityKey](xref:titleid.playfabapi.com.authentication.authentication.getentitytoken#entitykey) object on any login where you specify `LoginTitlePlayerAccountEntity` as `True`. | | **character** | This concept is unchanged. Your player may own characters, which can each contain some information. This is similar to [CharacterData](xref:titleid.playfabapi.com.client.characterdata.getcharacterdata). It's identified by the character ID (`CharacterId`) of the character. | | **PlayFabId** | Formerly this term covered both `master_player_account` and `title_player_account` concepts. Separating these concepts simplifies and clarifies the functionality. A player can interact with multiple titles in the same namespace. The player can have unique information in a different `title_player_account` for each title and a single `master_player_account` with shared data across titles. This enables cross-promotion of games and cross-game rewards. | ## See also * [Introducing Entities, Objects and Files](https://blog.playfab.com/blog/introducing-entities-objects-and-files) on the PlayFab blog. * [Entities quickstart](/services/playfab/live-service-management/game-configuration/entities/quickstart) ## Related topics - [Entities quickstart](/services/playfab/live-service-management/game-configuration/entities/quickstart.md) - [Game Servers and Lobbies](/services/playfab/multiplayer/lobby/lobby-server-overview.md) - [Create a lobby](/services/playfab/multiplayer/lobby/create-a-lobby.md) - [Migrate from Google Sign-in to Google Play Games in Unity](/services/playfab/identity/player-identity/platform-specific-authentication/google-play-games-sign-in-migration-details.md) - [Entity API Restructure Upgrade Tutorial](/services/playfab/live-service-management/game-configuration/entities/entity-api-restructure-upgrade-tutorial.md)