The GraphQL API also requires an additional permission read_customers to be enabled.
If you are using the custom application feature in Shopify You can enable this permission via your Shopify admin by going to the custom app and updating the permissions.
Key differences & risks
The Shopify GraphQL API retrieves and structures data differently from the legacy Shopify REST API, including the use of different internal identifiers for orders and related records. During our testing, we observed that if historical orders are included in the migration window, this can in some cases result in duplicated orders or mismatched updates.
To mitigate this risk, all migrations will be configured with a start date set to the migration date, meaning only new orders created after the migration will be processed via the new API.
What you must do before migrating
To ensure a smooth transition, all existing orders must be fully completed before the migration takes place. This includes:
- Orders being fulfilled
- Tracking information added
- Any final status updates completed in connected systems
If orders remain open or are updated during or after the migration window, there is a risk that certain updates (such as tracking information or order status changes) may not sync correctly between systems.
We highly recommend updating to Shopify GraphQL at a time of day where order volumes are at their lowest order levels.
How to migrate
Required checks after migration
Following the migration, customers are responsible for verifying that data is syncing correctly between systems. This includes, but is not limited to:
- Stock and inventory levels
- Product updates
- Order syncing
- Any other routine updates normally sent to Shopify
While the migration will be monitored, differences between the Shopify REST API and Shopify GraphQL APIs mean that issues may not always be immediately visible. Promptly checking and reporting any discrepancies will allow us to investigate and resolve them as quickly as possible.