AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

Ads
4.4K members online now
4.4K members online now
For questions related to Google Shopping and Merchant Center. Learn to optimize your Shopping ads
Guide Me
star_border
Reply

Migrated from Magento to Shopify and need to upload / switch to new feed file without disrupting ads

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Hello,

 

We migrated from Magento to Shopify yesterday around 5pm. In Magento, we had an extension which generated a .txt file that Google Merchant Center was scheduled to fetch every day at 3am. We paused the fetch (so I thought), knowing that Google would still have our feed from the previous day and just continue using that. Even though all of our URLs have changed, we have redirects in place so we were confident that everything would still work and we could use this "old" feed file for a few days while we figure out the best way to transition to our need Shopify feed file.

 

But - Google still tried to fetch it this morning at 3am, even though I thought I paused it. Obviously the file wasn't there and that fetch URL is no longer active. Luckily, nothing happened, it didn't overwrite our feed with blanks (which has happened before - disaster). It just says "1 ERROR: File not found" under Global Feed Issues. And we still have the same number of active items that we did yesterday before the migration. However, I am anxious to get our new Shopify feed file with correct URLs loaded into Merchant center and I need to make sure I do it the right way. Having a hard time finding guidance online, and the India based phone support was no help, *sigh.*

 

So, let's call my Primary Feed "Magento Feed". The input method is "Fetch". My new feed with my Shopify URLs is going to be a manually uploaded .txt file, for now. I don't see how to change the input method on an already existing feed - but this article from the community leads me to believe that we should not ever delete this primary feed, rather, we should edit it. 

 

My original plan was to create a new primary feed called "Shopify Feed", with input method as "Upload (manual)". Then somehow confirm that Google had processed those items, and delete the "Magento Feed". Now I am second guessing that.

 

All of my item ids are remaining the same. The new file just has new product URLs and image URLs, and some minor differences in product descriptions, titles, etc. I want a seamless transition, where items never disappear from our Merchant Center catalog, they just get updated with the new URLs and other info.

 

Any guidance on how to do this the proper way would be greatly appreciated! Thank you!

 

2 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by MosheTLV (Top Contributor)
June

Migrated from Magento to Shopify and need to upload / switch to new feed file without disrupting ads

[ Edited ]
Top Contributor
# 2
Top Contributor

(a) immediately pause all scheduled-fetches within the merchant-center-account,
and stop any automated-submits from the legacy website -- depending on the
details, one or both may be true; possibly contact whoever was supporting the
magento-software to be certain that no automated submits still exist.

generally, submitted data may be either pushed to google,
from the website via the api or ftp, or pulled by google
using a scheduled-fetch-url, or both -- all possible submit
methods must be investigated to prevent active data from
the old website from being submitted, in any way.

 

(b) verify the new website using the google-search-console,

then claim the new site within the merchant-center-account.

then, be certain the new website is up, running, and fully functional and
(c) manually upload the new feed data, with updated url's, using the existing
primary-feed -- be certain to verify that no id values have changed, before
any upload.

that is, simply use the existing, registered, (magento)
primary-feed to upload the updated (shopify) data.

there is usually no need to change the primary-feed registration
or use a new primary feed -- either use the same google-sheet,
or if possible, simply use the same file-name, otherwise google
will accommodate the new name without any delete or edit of
the existing primary-feed registration.

the registered-feed is simply a container to fill with the uploaded file data.

one, outlier, use-case is if the existing primary-feed is a google-sheet --
but the google-sheet will not, or cannot, be used to submit the shopify-data;
in that case, the existing primary-feed must be deleted and a new primary-feed
registered, for the updated shopify-feed-data -- either tab-delimited or xml.

review all results by carefully inspecting the feed-processing-tab
and clicking on the per-item-titles within the products-list-tab --
be certain all links land on the new website, without any redirects.

note that if any existing website is inactive for any length of time,
shopping-ads are still active, or the feed or website are not yet

ready for any reason, be certain to set all availability attribute

values to out of stock, or submit a feed-file that contains no items --
to avoid a disapproval or suspension -- redirects are not allowed
for shopping-ads and google requires the claimed website to be

up-and-running at all times, or all shopping-ads removed.

as an aside, verify, update, or remove, any existing feed-rules.

later, the submit may be automated --
either via the merchant-center with
an updated scheduled-fetch-url, or
server-side via ftp, for example.

 

View solution in original post

Marked as Best Answer.
Solution
Accepted by MosheTLV (Top Contributor)
June

Migrated from Magento to Shopify and need to upload / switch to new feed file without disrupting ads

[ Edited ]
Top Contributor
# 2
Top Contributor

(a) immediately pause all scheduled-fetches within the merchant-center-account,
and stop any automated-submits from the legacy website -- depending on the
details, one or both may be true; possibly contact whoever was supporting the
magento-software to be certain that no automated submits still exist.

generally, submitted data may be either pushed to google,
from the website via the api or ftp, or pulled by google
using a scheduled-fetch-url, or both -- all possible submit
methods must be investigated to prevent active data from
the old website from being submitted, in any way.

 

(b) verify the new website using the google-search-console,

then claim the new site within the merchant-center-account.

then, be certain the new website is up, running, and fully functional and
(c) manually upload the new feed data, with updated url's, using the existing
primary-feed -- be certain to verify that no id values have changed, before
any upload.

that is, simply use the existing, registered, (magento)
primary-feed to upload the updated (shopify) data.

there is usually no need to change the primary-feed registration
or use a new primary feed -- either use the same google-sheet,
or if possible, simply use the same file-name, otherwise google
will accommodate the new name without any delete or edit of
the existing primary-feed registration.

the registered-feed is simply a container to fill with the uploaded file data.

one, outlier, use-case is if the existing primary-feed is a google-sheet --
but the google-sheet will not, or cannot, be used to submit the shopify-data;
in that case, the existing primary-feed must be deleted and a new primary-feed
registered, for the updated shopify-feed-data -- either tab-delimited or xml.

review all results by carefully inspecting the feed-processing-tab
and clicking on the per-item-titles within the products-list-tab --
be certain all links land on the new website, without any redirects.

note that if any existing website is inactive for any length of time,
shopping-ads are still active, or the feed or website are not yet

ready for any reason, be certain to set all availability attribute

values to out of stock, or submit a feed-file that contains no items --
to avoid a disapproval or suspension -- redirects are not allowed
for shopping-ads and google requires the claimed website to be

up-and-running at all times, or all shopping-ads removed.

as an aside, verify, update, or remove, any existing feed-rules.

later, the submit may be automated --
either via the merchant-center with
an updated scheduled-fetch-url, or
server-side via ftp, for example.

 

Migrated from Magento to Shopify and need to upload / switch to new feed file without disrupting ads

Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭

@Celebird Thank you for your detailed reply! This was very helpful. Pausing the scheduled fetch on my "old" feed and uploading a new file manually to that same feed worked as I had hoped.

 

One follow up question; we would eventually like to submit our feed to Google Merchant via the Content API. So how would I make that switch, from a manually uploaded file, to Content API? It does not appear that you can switch the input method on an existing feed - so it looks like I would need to create a new feed when we are ready to do this. If this is true, do you have any advice for seamlessly switching to a new feed (with the exact same items / ids)?

Migrated from Magento to Shopify and need to upload / switch to new feed file without disrupting ads

Top Contributor
# 4
Top Contributor

1) Use a Plugin or management tool that sends data feed information using Google's Shopping Content API

2) Create your own private app and then build a custom system on top of the content API.

 

When you have the new feed method ready, you then need to delete the old feed, then recreate the setup in Google Merchant Center, which will allow you to choose a different import method.

 

Make sure the product ID's are identical, doing it this way will have no down time.

 

Hope this helps.

Twitter | Linkedin | Community Profile | Shopping Feed Tips From FeedArmy
Did you find any helpful responses or answers to your query? If yes, please click on ‘Accept As Solution’

Re: Migrated from Magento to Shopify and need to upload / switch to new feed file without disrupting

[ Edited ]
Top Contributor
# 5
Top Contributor

first, you're welcome.

id values are key to transitioning to a new submit method.

(a) if id values are identical, simply pause/stop any and all data uploads --
such as via scheduled-fetch, or server-side such as ftp -- then, begin
submitting the identical data with the new upload method, such as the api.

product-inventory data does not flow from the registered-feed
to the products-tab or shopping-ads unless some submit method
is active -- typically scheduled-fetch, manual-upload, or ftp; e.g.

if data is not resubmitted monthly, all items will expire naturally.

there is no need to delete the existing registered-feed
if all submit methods, using that feed, are stopped --
the feed will simply remain quiescent and associated

items will be removed after their expiration-date, unless

some (new) submit method is started.

although, deleting the feed will do little harm and is a best-practice --
the data will need to be re-submitted using the new method, in any case.

once an id value has been assigned to a physical inventory item, the id value
should never, ever change -- id consistency, for all physical inventory,
across all time, regardless of how data is submitted, is a best-practice
and highly recommended.

 

id are best considered as inventory sku, rather than tied to any submit method.

(b) if id values are different, then any transition will be more knotty.

first, to avoid duplicate-listing and related policy issues, the existing
primary-feed will need to be submitted with no items, and waiting until
all items are removed from the products-tab -- typically 72-hours or so --
is critical; only then, should the registered feed be deleted.

then, the new submit method may be implemented -- such as via the content-api.

also, if id values are different, all quality-related history will be lost;
click-through-rates, and similar quality details, will need to be rebuilt,
over time, and initially poor, or greatly fluctuating, results -- relating
to performance, impressions, clicks, etc. -- should be expected.

 

google tracks all shopping-ad performance based on id -- physical-inventory sku.

regardless of (a) using the same id, or (b) using different id,
the submitted data should be carefully inspected, for quality
issues and any other fundamental changes that may effect the
existing shopping-campaign -- for example, any product-groups
based on product_type, where all product_type values are not
identical, between the old and new product-data submit-methods.