[null,null,["最后更新时间 (UTC):2025-08-12。"],[],[],null,["# Start your migration\n\nIn this page, we provide guidance on planning your API migration.\n\nThen we take an overview of the steps you'll need to migrate.\n\nPlan your migration\n-------------------\n\n1. **Map your Content API for Shopping methods to Merchant API methods.**\n\n It's very helpful to clearly understand the new methods and resources you\n need for Merchant API.\n2. **Understand the most significant changes that apply to your migration.**\n\n We recommend reviewing and keeping in mind the following resources as they\n will be helpful for your migration:\n - **Migrate from Content API overview**: This details the major changes to be aware of in Merchant API\n - **Sub-API specific migration guides** : Review the specific sub-API migration guides you need as they provide critical information such as new field mappings. For an example, see [Migrate products\n management](/merchant/api/guides/compatibility/products).\n - [**Merchant API reference**](/merchant/api/reference/rest) provides the details of Merchant API resources and methods.\n - The **Quickstart** guide shows how to quickly start using Merchant API to create an account and upload a sample product.\n - **Feature-specific guides**: For new feature implementation or for more clarification, you can review the feature guides provided in the navigation.\n3. **Identify the sub-APIs that you plan to migrate and want to implement.**\n\n Determine two things:\n - The Merchant API features you need to migrate\n - The new features you want to implement\n\n Once you've done this, you can determine the amount of effort and a priority\n list of sub-APIs to work on.\n\n We recommend migrating everything, or as much as possible. If you aren't\n able to migrate your entire Content API implementation initially, due to\n importance and complexity, prioritize the following sub-APIs.\n - [Accounts](/merchant/api/guides/accounts/overview)\n - [Products](/merchant/api/guides/products/overview)\n - [Data sources](/merchant/api/guides/data-sources/overview)\n - [Reports](/merchant/api/guides/reports/overview)\n\n | **Note:** You can approach this on a case-by-case basis, depending on your integration type. For example, a feature such as [Inventories](/merchant/api/guides/compatibility/inventories) may be a higher priority.\n\nMigration steps\n---------------\n\n1. **Test different methods** to help you ramp up. We recommend using [Google\n APIs Explorer](/apis-explorer) to perform basic tests.\n\n The format of request URLs for Merchant API is \n\n https://merchantapi.googleapis.com/\u003cvar translate=\"no\"\u003e{SUB_API}\u003c/var\u003e/\u003cvar translate=\"no\"\u003e{VERSION}\u003c/var\u003e/\u003cvar translate=\"no\"\u003e{RESOURCE_NAME}\u003c/var\u003e:\u003cvar translate=\"no\"\u003e{METHOD}\u003c/var\u003e...\n\n2. **Leverage** our code samples and client libraries.\n\n To help reduce the implementation time and benefit from\n [gRPC](/merchant/api/overview#grpc-rest), use the [client\n libraries](/merchant/api/client-libraries) and [code\n samples](/merchant/api/samples).\n\n We also embed code sample snippets in our guides. For example, see [Add a\n product](/merchant/api/guides/products/add-manage#add_a_product).\n3. **Test simple user journeys.**\n\n Conduct user journey testing on all the sub-APIs and functionality you plan\n to migrate with the following goals:\n - Your migrated resources and calls have correct response results.\n - The error ratio remains low.\n\nPlan your roll-out\n------------------\n\nWe recommend the following approach:\n\n- Implement one sub-API or method at a time.\n- Implement to only a small segment of the business at a time.\n- Monitor for issues at all times.\n\nImplement your migration\n------------------------\n\n1. **Work on coding using the new resources and endpoints.**\n\n After initial testing and development of a release plan, integrate Merchant\n API into your workflows.\n2. **Monitor.**\n\n Prepare to address potential issues."]]