Troubleshooting Common Store Migration Failures
Store migration helps move business data from your original platform to SHOPLINE, but some records may fail when required data is missing, unsupported, duplicated, or not aligned with your SHOPLINE store settings.
This guide explains how to read raw migration errors, fix common source-data issues, retry failed items, and decide when to contact SHOPLINE Support.
Product and Category Migration Errors
Use this section when product, inventory, or category records fail during migration:
| Data type | Information shown in the migration result | How to use it |
| Product Categories | Collection handle, such as automated-collection | Use the collection handle to find the category or smart collection in the original platform, then check its conditions and sorting settings. |
| Products | Product handle, such as the-side-sleeper-s-cloud | Use the product handle to find the product in the original platform, then check images, option values, inventory, and related locations. |
| Raw error message | What it means | What to do next |
| column:product_category_id unsupport / product_category_id_with_descendants unsupport | The smart collection uses a standard product type condition that is not supported. | Update the smart collection conditions in the original platform, then retry the migration. |
| body.smart_collection: The required property 'rules' is missing from the object | The smart collection does not have any rules. | Check whether the smart collection conditions are empty in the original platform. Add valid rules, then retry. |
| SORTATION_CONDITION_INVALID | The product category sorting type is not supported. | This item may need product support before it can be migrated. Contact SHOPLINE Support if the category is important. |
| The product or category relocation failed, resulting in the inability to bind the category relationship. Please try again. | Some products could not be linked to the category because product or category migration failed. | Retry the failed item. If it still fails, check whether the related products migrated successfully first. |
| Failed to add product[At least one of the image ID or src should be valued.]; | The product does not have a usable image. | Add at least one product image in the original platform, then retry. |
| Failed to update product[You need to add option values for color_family]; | The product option color_family is missing option values. | Add the missing option value in the original platform, then retry. |
| activation inventory Error[System error, please try again.]; | Inventory activation failed, often because related locations were not migrated successfully. | Check whether inventory locations migrated successfully, then retry product migration. |
Abandoned Checkout and Order Migration Errors
Use this section when abandoned checkouts or orders fail during migration:
| Data type | Information shown in the migration result | How to use it |
| Abandoned Checkouts | Checkout number or checkout ID | Use the checkout number to find the abandoned checkout in the original platform, then check customer contact details, products, market, currency, seller note, and discount code data. |
| Orders | Order ID | Use the order ID to find the order in the original platform, then check payment, refund, market, currency, and discount details. |
| Raw error message | What it means | What to do next |
| Item in abandoned order is invalid. | The abandoned checkout contains a product that does not exist in SHOPLINE. The product may have failed migration or may have been deleted from the original platform. | If the product failed migration, migrate the product first. If the product was deleted from the original platform, this abandoned checkout cannot be migrated in this batch. |
| buyerinfo must contain userId, email or phone | The abandoned checkout does not include enough customer contact information. | Confirm whether the abandoned checkout has an email address or phone number in the original platform. If both are missing, the abandoned checkout cannot be recovered or migrated. |
| presentmentCurrency does not match market currency | The checkout currency does not exist in the current SHOPLINE market settings. | Check SHOPLINE market and currency settings, and make sure they match the original platform. |
| Creation failed: A-INVALID_ARGUMENT: Market CA not find | The market used by the abandoned checkout does not exist in SHOPLINE. | Check SHOPLINE market settings, and make sure the required market exists. |
| Creation failed: A-INVALID_ARGUMENT: invalid RelocateAbandonedOrderRequest.AbandonedOrder: embedded message failed validation | caused by: invalid AbandonedOrderRelocationDTO.SellerNote: value length must be at most 1000 runes | The seller note is over the character limit. | Shorten the seller note in the original platform, then retry. |
| Creation failed: A-INVALID_ARGUMENT: duplicate discount code: BOGOS-BPuyW55 | The same order uses the same discount code more than once. | Correct the discount data in the original platform. This type of abnormal data is not supported for migration if it is not fixed. |
| create refund order: ["SYSTEM_ERROR","OFC_123686_B1002"] | The refund amount is greater than the paid amount for the order. | Review the order in the original platform. If the refund amount is higher than the paid amount, the order cannot be migrated. |
Customer Migration Errors
Use this section when customer records fail during migration:
| Data type | Information shown in the migration result | How to use it |
| Customers | Customer email, phone number, or customer ID | Use the email, phone number, or customer ID to find the customer in the original platform, then check email format, duplicate contact details, email marketing status, and verified email data. |
| Raw error message | What it means | What to do next |
| email is illegal argument | The customer email address is not in a valid format. | Correct the customer email address in the original platform, then retry. |
| code=DATA_NOT_EXIST, alertMessage=data does not exist, debugMessage=data does not exist, suppressedErrors=[] | A service request failed or the required data could not be found. | Retry later. If repeated retries fail, contact your SHOPLINE account manager or SHOPLINE Support. |
| code=0003, alertMessage=There are different accounts registered with email and mobile phone, debugMessage=There are different accounts registered with email and mobile phone, suppressedErrors=[] | Different customer accounts are using the same email address or phone number. | Correct the duplicate customer data in the original platform. This type of abnormal data is not supported for migration if it is not fixed. |
| Email consent state is 'Subscribed' or 'Pending', email cannot be empty | The customer is marked as subscribed or pending for email marketing, but the email address is empty. | Add the customer email address or update the email marketing status in the original platform, then retry. |
| Verified_email is yes, email cannot be empty | The customer is marked as having a verified email address, but the email address is empty. | Correct the customer email data in the original platform. This type of abnormal data is not supported for migration if it is not fixed. |
Discount, Gift Card, Metafield, and Metaobject Migration Errors
Use this section when promotion data or custom data fails during migration:
| Data type | Information shown in the migration result | How to use it |
| Discounts and discount codes | Discount rule ID or discount code | Use the discount rule ID or code to find the promotion in the original platform, then check discount type, selected products, target customers or segments, amount, percentage, and duplicate codes. |
| Gift Cards | Gift card ID | Use the gift card ID to find the gift card in the original platform, then check whether the note is within the supported length. |
| Metafields | Owner resource, owner ID, namespace, key, metafield ID, and metafield type | Use owner resource to see what the metafield belongs to, such as PRODUCT. Use owner ID to find the specific product, page, or other resource. Use namespace, key, metafield ID, and type to find the exact metafield and check whether its type, value, or referenced resource is valid. |
| Metaobject entries and definitions | Entry handle, entry ID, metaobject name, definition ID, and definition type | Use entry handle or entry ID to find the specific metaobject entry. Use metaobject name, definition ID, and definition type to find the metaobject definition. If the error mentions a missing field value, check the required fields in that entry. |
| Raw error message | What it means | What to do next |
| graphql: Service call fail. | A temporary service request failed. | Retry later. If repeated retries fail, contact your SHOPLINE account manager or SHOPLINE Support. |
| Only one specified activity can be effective for a product in the same channel at the same time. | A product has more than one automatic discount active in the same channel at the same time. | Review the discount settings in the original platform, correct the conflict, then retry. |
| Items must be defined in 'customer get' when the 'customer get item all' is false | A discount is set to apply to selected products, but no product is selected. For Buy X Get Y discounts, the gift product may be missing. | Check whether the discount has selected products. If products are selected, confirm those products migrated successfully. |
| customers and customerSegments can not be empty at the same time | The discount targets specific customers or customer segments, but the target list is empty or did not migrate successfully. | Check the target customer or customer segment settings in the original platform. If customers or segments are selected, confirm they migrated successfully. |
| Percentage must be between 0.00 - 1.00 | The discount percentage is outside the supported range. | Update the discount percentage in the original platform, then retry. |
| The discount amount value must be between 0.01 - 99999999999.00 | The discount amount is outside the supported range or is 0. | Update the discount amount in the original platform, then retry. |
| The input value is already present. | The discount rule already exists. | Check whether the discount was already migrated. If it was migrated correctly, you can ignore this error. |
| Discount type is not supported. | The discount type is not supported for migration. | Currently supported discount types include order discount, product discount, Buy X Get Y, and free shipping. |
| Currently, it is not supported to set discount rules for both product and product variants | The discount is set at both product level and variant level. | This setting is not currently supported. Contact SHOPLINE Support if you need help deciding how to recreate the discount. |
| REQUEST_LIMIT_EXCEEDED | The migration triggered a request limit because the data volume was high. | Retry later, or contact your SHOPLINE account manager to request a limit increase. |
| discount code repeat | The discount code already exists. | Check whether the discount code was already migrated. If it was migrated correctly, you can ignore this error. |
| invalid GiftCardCreateOpenRequest.Note: value length must be at most 500 runes | The gift card note is over the character limit. | Shorten the gift card note in the original platform, then retry. |
| Metafield type is not supported. / type invalid. | The metafield type is not supported. | Update the metafield type in the original platform, or contact SHOPLINE Support. |
| key not allow number | The metafield value or key uses a number where it is not supported. | Update the metafield value or key in the original platform, then retry. |
| failed to get reference value | The metafield references another resource, such as an image, video, product, or page, that was not found. | Confirm the referenced resource migrated successfully, then retry. |
| Key must be at least 3 characters in length | The metafield key is too short. | Update the metafield key name in the original platform, then retry. |
| json: cannot unmarshal string into Go struct field ShoplineMetafieldDefinition.definition.id of type int64 | The metafield data could not be processed. | Contact SHOPLINE Support for help. |
| `single_line_text_field` must be consistent with the definition's type: 'boolean' | The metafield value does not match its field type. | Update the metafield type or value in the original platform, or contact SHOPLINE Support. |
| VALIDATION_ERROR: "metaobject_definition_id" validation value "gid://shopify/MetaobjectDefinition/9186738408" is invalid | The metafield references an invalid metaobject. | Confirm the metaobject data migrated successfully, then retry. |
| metafield definition already exists | The metafield definition already exists. | If the data migrated correctly, you can ignore this error. |
| Failed to get reference value. Please check if the related resources have been moved. | The metaobject entry references another resource, such as an image, video, product, or page, that was not found. | Confirm the referenced resource migrated successfully, then retry. |
| body.metaobject.fields.#n: The required property 'value' is missing from the object | A required metaobject field value is missing. | Check the metaobject entry in the original platform and add the missing value, then retry. |
| This field type is a meta-object but cannot match the definition. | A metaobject field cannot match its definition. | Confirm that the metaobject used as the field value migrated successfully. |
| definition.type: value does not match regex pattern `^[A-Za-z][A-Za-z0-9_-]*$` | The metaobject definition type name uses unsupported characters. | Rename the metaobject type in the original platform using only letters, numbers, hyphens, and underscores. |
Shipping and Location-Related Migration Errors
Use this section when shipping profiles, delivery rules, inventory locations, or inventory activation fail during migration:
| Data type | Information shown in the migration result | How to use it |
| Shipping and delivery | Shipping profile name | Use the profile name to find the shipping profile in the original platform, then check delivery rules and related products. |
| Raw error message | What it means | What to do next |
| Failed to set Profile[invalid ProductGroupSetReq.DeliveryLocationGroupList[0]: embedded message failed validation | caused by: invalid SetDeliveryLocationGroupReq.DeliveryPlans: value must contain at least 1 item(s)]; | The shipping profile is missing delivery rules, or related products did not migrate successfully. | Check whether the original platform shipping data is complete. If it is complete, confirm that the products assigned to the shipping rules migrated successfully. |
| activation inventory Error[System error, please try again.]; | Inventory activation may fail if related inventory locations were not migrated successfully. | Check whether inventory locations migrated successfully, then retry. |
Understanding Customer Statistics After Migration
Customer statistics such as total order count and total spent depend on migrated orders. If you migrate customers without migrating orders, the customer profile may not show historical order count or spending totals.
| Note: To display customer order count and total spent after migration, migrate orders together with customer data. |
Contacting SHOPLINE Support for Unresolved Migration Errors
If a migration fails and the error cannot be resolved using the troubleshooting guidance in this article, determine whether you should retry the migration or contact SHOPLINE Support based on the error message and recommendations provided.
- Retry later: Use this option for temporary service failures or request limits.
- Contact SHOPLINE Support: Use this option when the error remains after retrying, the error says the setting is unsupported, or the table recommends support assistance.