Pages

Wednesday, March 3, 2010

FTP Migration Tool Released

Earlier this evening we released the FTP Migration Tool. We are initially releasing the tool to Blogger in Draft so that we can closely observe the tool’s performance before releasing it to all users at www.blogger.com. If you’d like to give it a try, you may go to Blogger in Draft; if you have one or more FTP blogs in your account, you’ll see this alert:




This screencast walks you through the process:





A few notes about the tool:
  • The final post is in English only; translated versions for non-English blogs will be available next week
  • Once the migration is complete, you can delete the final post from your blog’s dashboard by going to Edit Posts and selecting the post for deletion. It will remain on your FTP blog so that visitors to that blog will know about the new location.
  • Once you migrate your blog to Blogger hosting, you won't be able to return it to FTP publishing
If you encounter any problems during your use of the migration tool, we’re collecting reports of problems here and will continue to reach out directly to help resolve any outstanding issues.

194 comments:

  1. I'm kinda confused, If I don't care about redirection, Is there any difference between this tool and Setting->Publishing->Switch to? because the tool doesn't work with my blog (hang at Verify FTP redirect) and I can't write new post until I return to blogspot

    ReplyDelete
  2. Hi,
    I've read all your posts, all the comments, but more I read more confused I am.
    So I have just one simple question: I'm using this domain name as my blog: www.traetta.com, Do I need to change something as Cname, Bname, Xname, ISP, UPS, USB, FTP, FBI, CIA, PHP, ASP, NBC, BBC... or wahtever ;-)
    Thank you

    ReplyDelete
  3. Migration tool looks very good with the rel-conocial etc. bits being the most useful bits, I guess. However, I still think it would be really good for you to explain when/why CNAME and A records are needed and whether there should be a full stop after ghs.google.com or not (I still haven't worked this one out yet and I think it will be the biggest stumbling block for us ftp'ers).

    ReplyDelete
  4. Or, you could migrate without having to modify cname or a-records at all with this tool.

    ReplyDelete
  5. Once you migrate your blog to Blogger hosting, you won't be able to return it to FTP publishing <<

    That least bit, if we don't like this set up, we CAN still export it to use in WPress can't we?

    ReplyDelete
  6. My blog is almost entirely a photo blog. Will all photos move to Blogger's hosting? Once we migrate, is there any reason to keep our blog and pictures and archive information on our ftp server? Or can we completely clear it out? I was confused with the back-linking stuff.

    My blog (redirects to my ftp):
    http://curtiswiklund.blogspot.com/

    ReplyDelete
  7. @Nick. That script looks great for a simple blog, but one of my sites needs the blog to be private. On the other hand, if I can get this blogger hosting sorted, it looks like a good solution. Thanks for sharing your script, though, I see some have already used it successfully.

    ReplyDelete
  8. I have read and watched this process from it's announcement and still feel it is the worst option Google could have offered it's dedicated users. Hosting my own site for over 10 years, before integrating Blogger as a "part" of the web site, have gain some of the best search engine listings with that site I have ever achieved and have been building sites for over 15 years. BUT over 3,400 pages ARE NOT posted or managed through Blogger so if I move the site I have to republish al those back through, back date to the original post date or the article on my original site, AND lose ALL MY SEARCH ENGINE LISTINGS,by redirecting all my hosting of my site to you.

    So, now I am forced with eliminating "part" (and I must admit a big part after using Blogger for years) of my site or find a way to move the entire content managed and posted through Blogger onto my own server and just go back to publishing everything through my own design tools, as I would let another company allow me to be put into this situation again with me having no control other than to just comply, as this site is a good part of income for my company... It is sad that Google has grown so powerful that they have the right to affect commerce around the World, with a simply, (in their eyes) decision made in Corporate Meetings. IT AFFECTS IS ALL AND ALSO AFFECT OUR ECONOMY WHICH IS SUFFERING ENOUGH!

    PLEASE, stop helping companies to build a valid site and income stream, then pulling developers that have integrated your tools because they have become successful with the use of them, right back away and forcing them to totally incur HUGE expenses in time and resources to try and get back what they had. HELP US DANG IT! We have helped you grow to be one of the largest companies in the World. Your practices affect our economy more than you realize... I do hope this will get to someone who really cares and be read by the committee that made this decision.

    Thank you for the tools you do provide for us that are essential in our businesses.

    Cris Draper

    ReplyDelete
  9. If what I understand from this video is correct. FTP users have to use a subdomain. That's not really the best option for me since I've been publishing my latest content on my index page for years.

    Is there any way around this or is it simply part of the process?

    ReplyDelete
  10. This comment has been removed by the author.

    ReplyDelete
  11. @Hushlight: If you don't care about redirection, you can go to Settings | Publishing and switch to Blogspot or a custom domain.

    @Bruce: I have always believed that the hard stop was required, but I believe some registrars account for people leaving it out.

    @Rob: Yes, you're always free to export the blog and move to another platform.

    @Curtis: No, images are not moved. If you want to shut down your FTP host, you'll need to find another location for your images and ensure that requests for those images are redirected. This migration handles the migration of the blog posts, not any files you have uploaded to your FTP host.

    @Tony: If you want to use the migration tool, we are requiring that you move to a subdomain. There are a number of reasons behind that, mostly having to do with the risk of users inadvertently rendering all uploaded files inaccessible if they were to switch over www from their FTP host to us. That said, if you're comfortable addressing that risk (by using our missing files host, for instance) then you're absolutely free to do so manually.

    ReplyDelete
  12. @Rick. Ahh, ok. NONE of the help files mention the hard stop. This definately needs changing (I've tried with and without and neither work, however!) It makes a big difference in the redirection with/without according to my DNS control panel.

    ReplyDelete
  13. This comment has been removed by the author.

    ReplyDelete
  14. How do you start the migration process over? I messed up and there's no way to go back a step. I'm stuck at choosing a sub domain and when I enter it, it tells me it's already taken. I know and I need to get to the next step.

    ReplyDelete
  15. @chestees: as noted in the post, please report any problems here.

    ReplyDelete
  16. My blog is already at the subdomain I would like "move" the site to. Is that possible or would I need a new subdomain name?

    ReplyDelete
  17. This comment has been removed by the author.

    ReplyDelete
  18. Do you have to publish the blog to a sub-domain or can it be pointed to a URL such as http://www.example.com/blog-goes-here

    ReplyDelete
  19. put in the full stop after ghs.google.com. and now my custom domain works! I also have the A records in place, but I think that these aren't necessary for me. PLEASE mention this in the help files as I can't see mention of them anywhere in the examples.

    So, as I understand it:
    if you're using a SUBDOMAIN you must put ghs.google.com. in the CNAME entries.

    if you're using the main www for the blog, then you need CNAME for the www AND the A entries set for the naked domain.

    Yes/no?

    ReplyDelete
  20. @Andrew: You cannot publish to a sub-directory (this and other questions are addressed in the FAQ.

    @Bruce: Yes, you got it. Didn't realize the help docs didn't include the period after the .com, I'll make sure they update that.

    ReplyDelete
  21. @Rick. Well, that confirms that today I have learnt much about DNS! Many thanks ;-)

    ReplyDelete
  22. Help docs updated. Thanks again Bruce, nice catch!

    ReplyDelete
  23. Okay here I am again. It has taken me days of arguments/imploring/cajoling different techies at Doteasy to help me set up the www2. configuration (and they lost all my records and had to retrieve from a backup) Sigh. AND I have, on Blogger,
    moved into a "custom domain" and set the missing file thingie to the same www2. address.

    So I've done what you told me to do. My photos are still gone (even though they're back on my Doteasy account/I can see them via FTP). Doteasy is now telling me I have to republish my blog in order for the photos to come back up.

    You have already told me, custom domains can't republish.

    1. How do I get my photos back.

    2. Do I ALSO need to use the migration tool for my no-longer-FTP blog?

    This has been the worst week of my life. Technically speaking.

    Thank you for your help (and expertise).

    ReplyDelete
  24. Okay, I recently purchased (before the Tool became available) a domain name through Google, and that is not showing up as one of the options in the Migration Tool. How do I fix this?

    ReplyDelete
  25. I just migrated my blog over to a new sub-domain and updated the CNAME. It went pretty quickly and worked really well. I still have the old ftp host around so the links can redirect.

    Thanks for putting in the hard work to make it pretty simple.

    ReplyDelete
  26. @metric152 You're welcome! Thrilled to hear it went so smoothly.

    ReplyDelete
  27. For folks with a lot of self-hosted and locally referenced photos, you may want to look at options for migrating to WordPress.

    ReplyDelete
  28. I changed from FTP to hosted a week or two ago, and now have my blog on blog.lumendipity.com
    is there a way to still automate the re=canonical and meta refresh on the old blog pages/links or is it just too late now and I really should have waited?

    ReplyDelete
  29. @Lumendipity: No, there's no way to retroactively insert the rel=canonical tags. If you are concerned about redirecting traffic, you can read up on .htaccess here: http://httpd.apache.org/docs/1.3/howto/htaccess.html which provides an alternative way to redirect visitors from your FTP site to your Blogger blog.

    ReplyDelete
  30. This may be a silly question; but, do I need to create subdomain name before I create a CNAME?

    http://www.thehrr.com/HRR_Fans_blog

    ReplyDelete
  31. @Lumendipity: Actually, there is a way. Set your blog BACK to FTP publishing, and use the Migration Tool. This is what I did. Blogger had even saved my settings!

    ReplyDelete
  32. I absolutely do use FTP for publishing my blog, and I did receive the email alerting me to the changes and have been following this blog awaiting the tool release.
    But I do not have a migration link/notification in my dashboard. Is this something I should be concerned about, or is this still being rolled out?

    ReplyDelete
  33. Rick, can I do what @Calion (right above me) said.
    Set my blog BACK to FTP and republish my blog,
    THEN change it and do the migration?

    I'm assuming I have to do the migration, or do you not need it with custom domain?

    ReplyDelete
  34. @Kris Gardner: A CNAME is what creates a subdomain. It's the term used to define where the subdomain is hosted.

    @pardalote: It's currently only on in http://draft.blogger.com/; it will be on in www.blogger.com later tonight or tomorrow morning. We're about to push a few minor fixes out to address 3 issues people raised last night and this morning in migrating.

    ReplyDelete
  35. OK, I understand that the migration tool requires that you select a subdomain.

    I'dlike to keep my own top (naked) domain name (thekillerattitude.com) for the blog.

    As I understand it I can "manually" use Settings->Publishing->Custom domain to do the switch.

    Q: Is this correct? Any specific things I should keep in mind? Anything with regards to the "redirect"/code insertion part of the video I need to consider?

    ReplyDelete
  36. @Rick:
    I emailed this question; but, you seem to respond quickly here; so, I'll ask it:

    I typed my CNAME on the "Publish to New URL" page of the setup before I created it. Now, that I've created it, when I clicked Resume then clicked Continue, I get the message "another blog is already hosted at this address".

    Please advise.

    ReplyDelete
  37. @Johan: If you want to keep the naked domain, hold off for a couple days. I'll write up a more detailed blog post showing exactly how to do that (manually; the migration tool isn't designed to address naked domains, for very specific reasons).

    ReplyDelete
  38. @Kris: Team is looking into it. Thanks.

    ReplyDelete
  39. I'm hoping there will be a thorough, written walk-through -- even if it's no more than the programmers' function spec. I don't want to be in the middle of a wizard, with minimal prompts, and not know enough to answer the wizard's question or do the procedure it asks.

    Also: The Google help page says we need both a CNAME and also four "A" records. It says the "A" records re-direct people who use the naked domain (without "www" or "blog" in front). But wouldn't that also block access to our original host for regular things like FTP? Are the "A" records necessary if the blog's URL is now going to be blog.mydomain.com and that is taken care of by the CNAME?

    ReplyDelete
  40. Scrolling back up and seeing an earlier comment by @Bruce: I guess my question is answered. If I migrate to blog.mydomain.com, I need only a CNAME. If I migrate to www.mydomain.com, I also need the "A" records, and presumably I engender risk that I will no longer be able to access my host. Since I want to take as few risks as possible, I will migrate to blog.mydomain.com, and put in only the CNAME record.

    ReplyDelete
  41. Okay, I tried the ftp migration tool and I'm already hosed up!

    I want to continue to use my custom domain name but when I got to the screen about selecting an address I chose the first one since there was no indication about choosing the second one to retain your domain. I now am stuck with a blogspot domain that I don't want.

    I did not continue the migration but the tool doesn't let me back out and start over. What a mess!

    Please how I back out and start over and choose the correct choice to continue using my domain name!

    Thanks.

    -CB

    ReplyDelete
  42. ..but I would strogly suggest the Google update this page to make it precise and clear when and whether "A" records are needed.

    ReplyDelete
  43. @Rick After I switched to Blogspot via Settings | Publishing, I lost all comments. it's really bad experience!

    ReplyDelete
  44. After moving my Blog from my FTP server to custom domain I discovered I cannot easily update an embedded google map in my template. I was accessing an xml file to set coordinates, but due to javascript restriction the file needs to be on googles servers. Not sure if I can get around this?

    ReplyDelete
  45. @Joe - That's a bit outside the scope of this blog, can you post to the help forums (feel free to send me a link) and I'll have the team take a look.

    @Hushlight - URL?

    @Michael - You're right, we'll update that page. I'll have a full written walk-through of the tool by early next week; been heads-down getting the tool tested and released.

    @Chris - Please file your issue here; we'll look into it and can reset the migration state for you.

    ReplyDelete
  46. @Discipleship Only way I could get this to work was to comment out the blogmeta data in the header of the template and then put in my own line. Leaving them both in (in whatever order) kept the blogger favicon (had to put in square brackets below to get the code to show....)

    [link rel="shortcut icon" href="http://www.whatever.co.uk/favicon.ico" /]
    [!--$BlogMetaData$--]

    ReplyDelete
  47. @Discipleship Also, if you don't want the navbar put this in your header (again, change the square brackets to greater than, less than signs)

    [style]
    #navbar-iframe { display: none; }
    [/style]

    ReplyDelete
  48. For me personally this tool is not helpful since like a lot of people, I blog at my "naked domain". So I'm eagerly awaiting that "naked domain" post you mentioned.

    ReplyDelete
  49. Case History

    @Rick Klau : Here is some feedback to consider when fine tuning the Blogger FTP Migration Tool.

    I switched the blog: www.jimwarholic.com/iforgot directory published blog on my server to iforgot.jimwarholic.com a subdomain blog hosted at Blogger, as a test case for the Blogger FTP Migration Tool.

    The details of the switch are published on the automatically published update page produced by the Blogger Migration tool. See, This blog has moved posting page for more in-depth analysis.

    The procedure had a couple of twists and turns that made life a bit interesting, but in the end, I think it went as well as can be expected at this time. I think there could be a few improvements in the process though, especially in light of someone that is having great difficulty with publishing FTP in the first place.

    1. I suggest letting us know up front, that if the blog has trouble publishing the updated pages via Blogger, that a ZIP file will be created to download that has the updated files, and subsequently must be uploaded via a standard FTP publishing program on your local computer or going to the CPanel or other hosting panel and uploading the updated files to the appropriate directories.

    2. Note that the archive files were not in the proper directory, when unzipped, because the blog was customized to store them in a different directory (like "archives") in the Blogger FTP administrative panel area to begin with. So, I needed to make sure I uploaded them to the proper directory.

    3. Observation: Very interesting that the PHP file names were maintained, and even a new posting, which I back dated to place it below (before) the "This blog has moved" posting, also had a .php file name instead of a .html file name. Is this a possible sign of things to come? For example, might we have in the future "PHP Includes"? That would be exciting!

    4. Changes: The Blogger Nav Bar no longer had the option to not show it from the Blogger administrative panel. Yes, I was able to hide it with CSS, but I had to adjust the top spacing of the template a bit for the new vs. the old. Is this a slight oversight of not having the option from the edit the HTML menu of not displaying the Blogger Nav Bar?

    5. XML Template Questions: If I decide to go to a new XML style template, will the file names still stay the same, with the same .php file naming convention? Will all subsequent new pages in XML templates and new blog postings be having a .php file naming convention if that is what I started with? Or, will the file naming convention be an option in the future?

    6. Procedure Fine Tuning: At the point where the FTP migration tool came up to download the ZIP file, the main enter button was still saying something, like "continue" or something like that, which didn't make sense at that point in the procedure.

    7. I am sure I am forgetting about something in this comments section, but you can read about it over here at: I Forgot What I Was Doing.

    Hope that helps.

    Regards,

    Jim W.

    ReplyDelete
  50. Successfully migrated last night. Looking back, don't know why I waited for the migration tool, other than, I guess, for the back-up to work fully. I already post at a sub-domain (sheer dumb luck I would presume rather than crafty forward thinking on my part) and wanted to retain the same sub-domain.

    I do not believe the tool handles this very elegantly. When I move from blog.domain.com at my FTP location to blog.domain.com at custom domains, it cops out and asks me to go the "advanced" route. Even after I set the CNAME to point to Google, I just cannot get the wizard to go through the remaining steps.

    Since I already had the backup, I just had to switch back and forth between the *.blogspot.com and custom domains (a few times) to get rid of the 404 error at Google. And since the CNAME had already propagated, the blog popped back into existence about 10 minutes later.

    Now if only someone can help fix the security token error, so that I can see about moving off templates into layouts. I'll bet templates will be the next to go.

    Thanks to all and @Rick for the comments on this blog - they helped.

    -- nrk

    ReplyDelete
  51. @Rick
    When I created a CNAME (fansblog) yesterday, my webhost automatically added the '.'

    I was able to click to Continue during the 'Publish to new URL' section; however, I do not see the "Hosted by Blogger" message. Instead, I'm asked to add a CNAME -- which I already did.

    ReplyDelete
  52. i also have many pictures on my blog....and am not shutting down my site host....so what steps shall i take to ensure my pics wil be on my new blog.?? how do i redirect my images?......you wrote this earlier

    @Curtis: No, images are not moved. If you want to shut down your FTP host, you'll need to find another location for your images and ensure that requests for those images are redirected. This migration handles the migration of the blog posts, not any files you have uploaded to your FTP host.

    ReplyDelete
  53. We did the migration on all of our blogs and it went smooth. We have multiple blogs and have a php setup that pulls in the lasted blog that has been posted to into our regular site as a widget teaser. Now all of our blogs have as the first post a redirect notice. First I'm wondering how long does that stay up before it goes away? Second it is pulling in this code into our widget teaser: __FTP_MIGRATION_NEW_URL__ Any clue on what I can do to get rid of that or fix it?

    ReplyDelete
  54. Nobody can help me? I have just one simple question: I'm using this domain name as my blog: www.traetta.com, Do I need to change something? Can I still use it as it is? (I know nothing about everything you are talking about)
    thanks

    ReplyDelete
  55. Rick, I have a similar problem as "Hushlight." Today I switched publishing from Blogspot to Custom Domain. All seemed well until I discovered all entries now say "0 Comments." They have not reverted to "needing moderation," on that screen are still only the comments I really hadn't approved. I exported the blog, and while I don't know XML I could still see the text of the moderated comments there. Since the FTP Shutdown FAQ confirms that comments will migrate, can you help? Thanks in advance!

    Old URL: volguus.blogspot.com
    New URL: blog.huegel.com

    ReplyDelete
  56. This comment has been removed by the author.

    ReplyDelete
  57. Immediately after getting the "migration alert" on my dashboard pages, my FTP posting is failing. Also my "edit this post" pencil isn't showing up.

    Perhaps it's a coincidence.

    But I'm currently not feeling big feelings of trust and love for Google. I'm migrating to WordPress so that I can keep all my files on MY server, under MY control.

    Basically, as of May 1, "Goodbye, Google, and thanks for all the fish."

    ReplyDelete
  58. @NT: Hey, just a guess, but if thousands of folks all got that same alert this morning and many of them did the migration (which apparently updates the entire FTP blog), then Google/Blogger's servers may be tapped out for a while. Esp. if Google's been trying to compartmentalize/reduce FTP traffic.

    I'm glad we still have 7 weeks to migrate.

    ReplyDelete
  59. I migrated one blog successfully; however, when I tried to migrate a second blog, I got this message:
    "There was a problem verifying the completion of your FTP republish. Click here to download a ZIP file archive of your blog, which you can manually upload to your FTP host."

    What do I need to do?

    ReplyDelete
  60. Question Rick. I'm handling this migration for a client. I just watched your migration tool video and all seemed clear. However, when I logged in and used the "start migration now" link I was only given one ftp blog when there should be more than one. How do I start the migration for one of the blogs which is not first in the list? (FYI, I had already done the DNS propogation, would this make blogger think that it was not an ftp blog anymore). I still need to meander through link redirects and a feed to the web site from the blog.

    ReplyDelete
  61. @Rick: I have a JS script that generates a google map with pins for the posts (I have a travel blog at dean.katsiris.com). If I move my blog, the script won't move and thus will be located on a different server than the blog. Will this create a problem (cross-site scripting and so on) for me? The map is an integral part of my blog and I plan to make it even moreso when I return from my latest adventure so abandonment of this feature is not an option. Thanks.

    ReplyDelete
  62. I migrated three blogs today and all three have the same issue: the site feed has appended the old blog page file name to the blog title link in the feed XML files. For example, on one blog the title link in the XML file should be "http://news.moondogfreepress.com/", but it is incorrectly showing up as "http://news.moondogfreepress.com/blogger.htm". This sends visitors to a nonexistent page. How can I (a) fix this error on these blogs, and (b) prevent it from happening in future migrations.

    ReplyDelete
  63. @Kris: If you see the final post at the FTP blog and can see the rel=canonical code when you view source, then you're all set.

    @WebDi, @Dr. Moondog: Please report your problem in the form (linked to in the body of the post) and we'll look into it.

    @Dean: Don't know, suggest you set up a test blog to see before you migrate.

    ReplyDelete
  64. If an image has been put into an FTP blog by a link -- "Or add an image from the web" option -- will the link still work after the blog is migrated?

    ReplyDelete
  65. The only reason I'm using ftp is because my site starts at a static page (www.example.com) and I have several blogs that link from that page (blog1.example.com, blog2.example.com, etc.). When I migrate, can I still do this? I know Blogger just introduced static pages but the pages are not at www.example.com. The static pages are at www.example.com/static-page.html. Is there a way I can make a static page at www.example.com and have my blogs at blog1.example.com, blog2.example.com, etc.?

    ReplyDelete
  66. I don't know if you did anything, but I switched my Publishing back to Blogspot (which still showed 0 comments on any post), then back again to Custom Domain whereupon all my comments were restored. Thanks for whatever you did!

    ReplyDelete
  67. I wonder (based partly on @Volguus) if it would be a good idea to migrate to a blogspot blog, THEN to a custom domain. It might mean there would be a fallback should glitches occur. Just thinking out loud. I imagine most new blogs start on blogspot anyway, then get "customized." Again, just thinking out loud...

    ReplyDelete
  68. I'm in the process of trying to migrate my site, but after clicking "CONTINUE" on the "Backup Blog" page, it's hanging forever saying "preparing blog for migration... this might take a few minutes."

    A few minutes is a few hours now. I can't back up to publish via FTP anymore. Please advise!!

    ReplyDelete
  69. It would be a good idea for Blogger to publish running stats on the migrations. All we hear about on this blog are the glitches and blowups. I would love to know that there have been hundreds of successful ones. Just saying.

    ReplyDelete
  70. @Steve: Yes.

    @Charles: You can continue to host content w/a separate webhost at www.domain.com, and have multiple blogs hosted by Blogger at blog1.domain.com, blog2.domain.com, etc., and link to those from www.domain.com.

    @Douchebag1: Report your issue here: https://spreadsheets.google.com/viewform?formkey=dEExb2c4dHNsTmp2cS1RQml2U0lUUmc6MQ

    @Michael: A Google search will show lots of successful migrations.

    ReplyDelete
  71. @Rick

    I filled in your spreadsheet. This experience has been awful so far. I have no idea why you would deny the ability to move back to FTP publishing for anyone running into problems with the migration. My site is now completely frozen in both directions.

    ReplyDelete
  72. I started the migration process and then realized I needed to set up my custom domain and started to do that. When that was finished I couldn't get back to the migration process. The alert disappeared from my dashboard, as well as any links to the migration. I've filled out the spreadsheet too. What happened?

    ReplyDelete
  73. It appears that I started the migration process and then clicked on links to change the settings manually. Is there a way to go back? I didn't backup my old blog and now I can't get to it since I already changed the custom domain settings.

    ReplyDelete
  74. Hi. Ok, I have done this process, and all went smoothly for me, except... the old blog is not being re-directed to the new.

    The new "this blog has moved" post was automatically put on there ok, announcing the change, but no matter how long you wait, there is no redirection happening. Anything I can do?

    ReplyDelete
  75. I must echo a few of the comments here and a warning about not being able to go back to FTP publishing when possibly toggling to a Blogger published blog prior to running the migration tool.

    I was about to perform a migration for a client, but wanted to see what the original Blogspot subdomain was prior to the switch from FTP to a Custom Domain name. Once I made the switch, low and behold, I was not able to switch back to a FTP published blog, and hence could not perform the desired FTP migration run. The option was no longer present in the administrative area. This resulted in more than a sigh.

    Fortunately the blog was located in a sub directory off the main website, and was relatively small in size, and I was able to create an .htaccess file with a permanent redirect of all the files from the sub directory of the main website, to the new custom domain name website using ww2 as the new subdomain name.

    As an added note and reminder to others, give the CNAME a chance to propagate online after it is created, and before switching to this new Custom Domain name at Blogger. The new CNAME Custom Domain Name took about ten or fifteen minutes to propagate when I created it at the Web Host Manager, and for it to pop up as the new blog in Blogger when viewing the website for the first time.

    By-the-way, the original blog was created with using PHP file names, and the custom domain name still maintained the PHP file names (ending in .php instead of .html). This answered my previous question and this is good.

    I would strongly suggest allowing folks to go back to FTP publishing during this brief transition period in case someone toggles the blog to Blogger hosted like me and others have already done so. Most folks are not going to know how to create .htaccess files, nor are they going to know how to add redirects using the various commands.

    This is not going to endear folks too much, and I think that is quite an understatement.

    According to Jim

    ReplyDelete
  76. My blog used to host under FTP but not knowing that you guys gonna launched the FTP Migration Tool, I went to manually switch the host to blogspot.com

    Is there any ways that I can re-published again using the FTP migration tool so that all my webpages can have the rel=canonical tags?

    Please help thanks!

    ReplyDelete
  77. Rick...

    As others above have posted, I want to keep my domain name as it is: www.mrconsumer.com or mrconsumer.com . I don't want blog.mrconsumer.com or any subdomain, unless somehow readers who enter mrconsumer.com will magically wind up at the right place. All my posts are on the homepage of mrconsumer.com.

    Whatever you come up with to better explain what needs to be done to accomplish this would be most welcome. I urge you to make that process AUTOMATIC rather than manual if at all possible.

    Thanks,
    Edgar

    ReplyDelete
  78. I second Steve's comment about the re-direct: the only thing that happens is, after 30 seconds, it re-directs to the same page rather than the newly migrated blog.

    ReplyDelete
  79. Hi,

    I was publishing using FTP
    I changed into Custom Domain Some time ago (when you first that you are going to phase out FTP)

    Now, How to run this tool
    www.nellaimedicos.org
    www.first-test-series.com

    ReplyDelete
  80. Rick, I switched schmuckraker.com to blog.schmuckraker.com, I actually did it without going through the migration, I am going to redirect my .com on my server to the blog .. but I have one concern I should have asked before I switched: I intend on keeping my hand-coded HTML design. Will that be possible after the official migration? Right now I am using a custom domain with the blog

    Please let me know, either email me or comment on here

    ReplyDelete
  81. I've filled in the spreadsheet, and I'm having a very strange issue. I went through the migration tool yesterday and everything appeared to work fine. I even saw the blog at blog.backyarddiyguy.com for a few minutes, and then it disappeared, showing a Test Page for Apache, and 404 errors for all of the sub pages. Then it came back, then it disappeared again. It has done this again this morning. This is so very frustrating, and thank goodness it's only my father's new (and very small) blog. I have another blog to migrate, but I'm not very confident in the process at this point. And I'm glad I didn't use the tool on my own blog, I just set up a new one entirely with a link to my archive at the old ftp site.

    ReplyDelete
  82. PLEASE clarify...if I just say Fuck it and decide to RETIRE my ten year old blog, http://www.FRESHCHAOS.com, I can DO NOTHING and the old posts will remain online as they have been written...?

    And can I begin a NEW blog using the NEW non-FTP arrangement wihtout changin over old blogs on my blogger acct?

    Many thanks...capnchaos

    ReplyDelete
  83. It would be great if you could switch back to FTP during the transition period; In a an unpublished comment I said that when asked for my own domain name I entered the same address. I ended up on a page for manual changes. I could only hit "finish" or "back". I hit the first one and I got the message that the migration was complete. BUT my posts don't appear (even if it says it was a success) and I cannot even go back all over again since the migration message has disappeared from my dashboard. I've got 7 years of post I want to continue!!

    ReplyDelete
  84. To be honest, I think a lot of FTP users want to conserve their own address. The option is supposedly given but you insist on changing our address. I don't get it, added to the problems I mentioned.

    ReplyDelete
  85. @Rick

    Please please PLEASE let people temporarily go back to FTP publishing if they've started migration and it froze in an endless "preparing blog for migration... this may take a few minutes" hang.

    I realize you're trying to force people to stop using FTP publishing, but come on man, this is ridiculous. Let me go back to FTP publishing while you get your migration tool to actually work.

    Please help.

    ReplyDelete
  86. Yes, we are working on manually resetting migration status for anyone who got stuck in the process. We'll be reaching out to those who've logged their issue on the form asap.

    ReplyDelete
  87. I am not clear about after this is done: do I still log in to Blogger and publish blogs here? I have also registered this blog through Bulk Register. If I want to send people to my blog which link would I use, the old Blogger one or the Bulk Register one? Please help.

    ReplyDelete
  88. I am trying to migrate my FTP blog at www.friday-fun.com/blog using your instructions. I want to use blog.friday-fun.com as the new URL.

    1. When I started your process and added a CNAME on godaddy for blog.friday-fun.com -> ghs.google.com my whole site became unaccessible for around 30 minues - is this expected?

    2. The next step to create the 4 A-Name records - is that necessary if my blog is only a subdomain of my main site? It looks like the A Name records will point the whole of friday-fun.com to Google when only blog.friday-fun.com needs to point there. Please confirm as your instructions don't explain this as far as I can see.

    3. I cannot make out from your info whether the existing blog records, images, video embeds etc etc will all MOVE To google hosting or not (will I be able to delete the old /blog directory from my own host or not? Given the message you add says to update feed subscriptiosn to my OLD FTP site which seems back to front - again I don't see any info on this in your instructions.

    Thanks
    Mike

    ReplyDelete
  89. @Melissa: Thanks for noting the issue on the form. We'll be reaching out shortly.

    @Jim: Thanks for the feedback. First off, you're right: if you switch the blog off of FTP publishing, then the system will no longer consider it an FTP blog, which means it will no longer show in the migration tool. We're trying to avoid wholesale switching in and out of FTP - not because we want people off of FTP early, but because of the likelihood of confusion about what state the blog is in, whether they've migrated, etc. That said, we want to make migration available for as many as possible, and will figure out the simplest way to restore FTP status so that folks like you can initiate the migration. (Though as you note, .htaccess is just as effective, if not moreso, and involves fewer steps.)

    @Edgar: I'll be writing up a post next week that will detail how to switch from www.domain.com (FTP) to www.domain.com (custom domain).

    @Kris: Which browser are you seeing this behavior in?

    @Bruno: There is no way to run this tool if you've already moved off of FTP.

    @schmuckraker: Yes, you will be able to keep your custom design.

    @Doodle-head: Sounds like a DNS problem, thanks for reporting it on the form. We'll look into it.

    @the Chaos: You're correct, you do not need to do anything. Leaving the FTP blog as is will do exactly that - leave the files in tact. If you choose to set up a new blog, you can link to it and there will be no issue.

    @Fiddler's Green: I've responded elsewhere on the blog and in the FAQ - using the migration tool and keeping existing URLs was fraught with too many opportunities for users to inadvertently cause their non-blog content to break. Since we didn't want to break things for users, we built the tool in a way that would avoid that. That said, as I've noted above: I'll have a brief post up next week that'll explain for users who want to keep www.domain.com as their address.

    ReplyDelete
  90. I clicked on the the "start migration" link and when the next page loads there it lists no blogs that need to be migrated. That does not seem right.

    ReplyDelete
  91. Further to my post a couple back - my migration "completed successfully". However all images are broken and my main site no longer seems to work properly - links to pages no longer find pages. I'm suspecting the A Names should not point friday-fun.com to the IPs but blog.friday-fun.com should - I don't understand all this stuff but do understand my site is now broke and my supposed 'successful' blog migration has broken images.

    Help to unbreak my lovely blog and site appreciated. This is a test as I have a massive an much mroe important blog to do if I can make this easy one work.

    ReplyDelete
  92. @Rick: How can you explain, having migrated (and not being able to revert to what it was) that my new posts don't appear? I've sent en email to help section but I'm sure I'm not the only one to which it happened.
    About your upcoming post, will users (such as me eh eh) be able modify some changes in case we need to?

    ReplyDelete
  93. @Rick --

    Thanks for the quick responses, I greatly appreciate it.

    Can you advise on if you'll be able to set up a "restore original FTP settings" button on the migration panel? Anything to back me up so I can go back to posting while you iron out the bugs on the migration tool would save me an incredible amount of stress.

    Thanks in advance,

    ReplyDelete
  94. @Rick: Just an FYI, it turns out that I can use scripts hosted elsewhere without a problem. Except now it seems there is another new feature stopping me from migration: auto-pagination. If I could turn it off I'd be ready to move.

    ReplyDelete
  95. Does the migration tool and the included backup tool still have the 5000 posts limit? How can I export a blog with more than 10.000 posts in one piece?

    ReplyDelete
  96. When using a subdomain, do we need to put in the A records??

    ReplyDelete
  97. Rick, I guess you gave up on me. Doteasy has created this directory for me: /public_html/www2 to match my setup in Blogger. But I still don't know if I need to use the migrate tool on Blogger's side. I've converted to custom domain.
    (and lost my ability to republish) but apparently Doteasy has worked around that? I really need help and you are ignoring my posts above.

    ReplyDelete
  98. Really frustrating this.

    I have three subdomain sites to shift

    blog.fallondpicks.com
    jobs.fallondpicks.com
    tradingsystem.fallondpicks.com

    I first tried to migrate my blog at blog.fallondpicks.com to markets.fallondpicks.com. I Assigned the CNAME for the markets subdomain to ghs.google.com. (with the period after 'com'). I also added the four DNS to the markets subdomain in my DNS Manager. And then - nowt. No error message, nothing to say what I've done is right or wrong. I am expected to wait hours for the DNS to 'update' before reporting an error! I could be waiting days for something which will never update. It's already a couple of hours and nothing showing. Maybe this is fine but it's not reassuring.

    I have a blog where my new posts don't show. Worse still, my non-migrated blog at jobs.fallondpicks.com doesn't work without the 'www.' prefix. Nor can I post to it; so it's total bust.

    It's bad enough losing the original domain name (so now I have a blog which I can't call a blog in the URL), but my blog has entered a Google limbo with no clues as to how to troubleshoot to get it working again. Your video conveniently goes straight to the "Hosted by Google" because the critical stage most will struggle at is held at the hosting ISP.

    I'm quite happy to migrate - but when the process of migration "breaks"/fails to inform half-way through it's leaves me totally frustrated.

    Where are my blogs!!! Why can't the migration tool tell me it' can't detect the DNS or CNAME entries so I know they are incorrect. Maybe DNS or CNAME doesn't work for subdomain blogs???

    I can understand the need to get people of FTP and most of my blogs are non-FTP 100% Blogger blog, but FTP bloggers are the ones who have been blogging for years and likely have the readers to make it worthwhile blogging for as long as they have (and I'm sure the Google Adsense cut to Google is worth the pain). We can't afford to be down for long as readers will simply stop visiting and 5 years of work will be wasted all because of an inadequate migration tool.

    There needs to be better feedback from the tool.

    Thank you,
    Declan

    ReplyDelete
  99. I routed Blogger to my custom domain. Do I still need to worry about this whole FTP issue? Is it possible not to have to do a migration because I have no blogs listed to migrate?

    ReplyDelete
  100. @bevjackson Not ignoring you, had a family emergency. When we were last discussing this, you were getting doteasy to restore your uploaded files and images from a backup, and then setting up a CNAME subdomain that would point to those files. Have they set up the subdomain?

    @Declan Did you report these issues in the form? I'm catching up on reported errors and will take stock of where we're at (and who remains stuck) by morning. We'll be caught up by tomorrow.

    @Blue Collar Todd: If you have already switched to a custom domain you're all set.

    ReplyDelete
  101. @Christian There is no limit of 5000 posts per blog, we have many blogs with tens of thousands of posts.

    @moviemakerrules A Records are only for "naked" domains (http://domain.com/), if you're using a subdomain other than www then you do not need the A Records configured.

    @Dean: What about auto-pagination is blocking your move?

    @Dr Effingpot: You should not configure A Records unless you're using a naked domain (http://domain.com). If you used the migration tool, then you should not be configuring A Records at all.

    @Fiddler's Green: Don't know why posts wouldn't be showing, I have the team looking into it.

    ReplyDelete
  102. Reading between the lines, it seemed that driving a lot of concern was the problem of address change. So I decided to check it out by converting one of our lesser blogs to a new blogspot name. I also changed the name of our RSS feed. On my old FTP page I put a clear link to both new addresses. On our major blogs I plan to remind readers every few weeks of what is happening so they'll know what to do if they can't find us. Will let you know how this is working - Sam at The Progressive Review

    ReplyDelete
  103. Hi Rick,

    My CPanel will not allow me to put the period (or dot) at the end of ghs.google.com. it will only accept ghs.google.com and the DNS configuration window does not change to Hosted By Blogger.

    When I browse to blog.mississauga4sale.com I now receive an error.

    Is there some other thing I should be doing or should I ask my host to manually set the CName to ghs.google.com. ?

    Should it work for ghs.google.com without the . at the end and I just have to wait longer?

    Thanks
    Mark

    ReplyDelete
  104. in addition to my post above, my current CNAME in my CPanel is set to ghs.google.com and if I browse to http://blog.mississauga4sale.com I now receive an error. If I browse to http://www.blog.mississauga4sale.com with the www it resolves to my blog.

    BUT, I still don't receive the "Hosted by Blogger" in the migration tool.

    Am I still doing something incorrect?
    Thanks
    Mark

    ReplyDelete
  105. Hi Rick,

    Let me join the others and say, as loud as I can, that this is very very frustrating!

    Here is my question: how can I REstart the migration tool?

    I started the migration tool just to try it, and migrated to somethingtemporary.blogspot.com. Now i don't have the option to restart it all. What I want to do eventually is to keep the same address: blog.waysofseeing.org

    And from what I understand, in order to do that I'll have to use my custom domain?

    How can we keep the exact same address?

    ReplyDelete
  106. Okay - stage 2 of my Odyssey

    Blog.fallondpicks.com has migrated to Markets.fallondpicks.com - so on to the next step.

    However, next step fails and states I have to manually FTP the files (all 5 years of data!!). But where am I updating these files too? Is this updating code on my old subdomain (thereby overwriting it), or is this going to my new subdomain? The tool-tip doesn't tell me where these files are to go???

    I have logged these bugs - but I'm going another day without a blog...

    I thought this was migration tool was tested?

    Declan

    ReplyDelete
  107. Stage 3 of the Odyssey

    So the Migration Tool is telling me to manually FTP my files because it can't do it for me.

    I use my 'TradingSystem' to 'Strategy' blog as a test for the transfer since it's small so should be quick to upload.

    First thing I do is FTP's my files to the new subdomain. Well - that didn't change anything as the Migration tool is still asking me to manually upload my files. But this is easy to undo.

    Next I FTP'ed the files to my old subdomain - presumably these new weekly HTML archive files are the critical ones for the redirect since they didn't exist in my old blog. Well, uploading all of these files brought no change either. I'm still been asked to FTP my files

    I'm stuck - can't go forward, can't go back. Can't verify so now what?

    How to I get to the last step? Do I need to wait x hours for this step to verify...

    I have wasted hours trying to sort this and the only thing my site visitors are going to see to my primary blog a "Google Not Found Error".... at blog.fallondpicks.com. Bye Bye readers....

    I'm out of options with a set of blogs which are broken and unfixable (by me at least).

    Declan
    This has been filed in the bug spreadsheet report

    ReplyDelete
  108. FYI

    markets.fallondpicks.com resolves to blog (partial migration)
    www.markets.fallondpicks.com gets a Google Not Found error
    www.blog.fallondpicks.com gets a Google Not Found error

    Declan

    ReplyDelete
  109. Mi dirección del blog es http://www.mydomain.com/blogx/blogx.htm y no es http://www.midomain.com/blogx/index.htm

     ¿funcionará La herramienta de trabajo para nuevo dominio http://blogx.mydomain.com ?

    El perdón no se Inglés

    ReplyDelete
  110. My direction
    of the blog is http: // www.mydomain.com/blogx/blogx.htm and is not http: // www.midomain.com/blogx/index.htm

    ¿Will The tool of work work for new domain http: // blogx.mydomain.com?

    The pardon not Englishman(English)

    ReplyDelete
  111. This comment has been removed by the author.

    ReplyDelete
  112. Reposting to fix typos...

    I have completed the migration of my two blogs and have a few comments and questions I can't find answered (and see others asking too, so you may want to review them).

    1. One of my FTP Blogs was a 'private' one that was not indexed by Google or other search engines - does this status migrate across too? (I want it to remain 'private').

    2. Where are my existing (original/old) posts stored now - still on my server or can I delete them after migration?

    3. Where are new posts going to be stored - presumably not on my server any more so I end up with a combination of two places where things are filed? And I don't need to backup new posts?

    4. When the blog is merely a subdomain and moves in my case from www.friday-fun.com/blog to the new blog.friday-fun.com then you don't need to change A Names - though the instructions seem to tell you to. You ought to review the notes on that as others made the same mistake following the instructions as I did.

    5. When the migration stage one completed my blog, main domain and then images all broke. An hour later they all reappeared. You may want to warn folks about that - I see some posts complaining then being OK after waiting a while. This is not a good result to readers of ones site, of course! (And may be linked to the A Name ambiguous instructions in my case)

    ReplyDelete
  113. Oh and

    6. Why does the migration leave the FEED on my old FTP hosted space on my server? I expected that to move somewhere else?

    The migration message post that appeared on my blog says ...

    This blog is now located at http://blog.friday-fun.com/.
    You will be automatically redirected in 30 seconds, or you may click here.

    For feed subscribers, please update your feed subscriptions to
    http://www.friday-fun.com/blog/atom.xml

    Does this not mean that when I post from now on - blogger is FTPing an updated atom.xml file to my site? Which I thought was the opposite of what this exercise was trying to achieve.

    Confused by that one.

    ReplyDelete
  114. And finally ...
    7. There seems to ba an unreviewed COMMENT from before the migration that needs to be REJECTED or PUBLISHED now. This function no longer works with a comment that came across with the migration. (Whichever option I select it does nothign and returns me to Review mode). Oops! Is there a way to get rid of it somehow?
    Thanks
    Mike

    ReplyDelete
  115. La verdad, es que sigo decepcionado.
    Cada día me gusta menos Google. A la que encuentre otra alternativa mejor para Blogger migro el servicio.

    ReplyDelete
  116. I have 5 blogs and publish them on my domain.
    today I migrated http://www.realfiesta.com/bookclub.htm to http://kitap.realfiesta.com/

    Now I can see and publish to my blog on this new address.

    But on the Migration tool, i didn't get to see HOSTED BY BLOGGER picture and couldn't continue to third step. However the blog works on new DNS as I said above.

    How long will it take HOSTED BY BLOGGER sign to appear?

    thanks.

    ReplyDelete
  117. I'm disappointed.
    I'm a blogger from Germany. My ftp-host is one of the most common providers: Strato. However, they don't offer the CNAME manipulation.
    So I agreed to move the blog to blogspot. Now, Blogger changed the German Umlaut-letters: Ä,Ö,Ü into some unreadable stuff.
    What now?

    ReplyDelete
  118. @Rick: Auto pagination isn't directly blocking my move in some sort of incompatibility way; rather I have a travel blog that relies on people being able to see all the posts when they look at labels (Australia, for example) for the map to be navigable.

    So if I can't find a way to have all the posts on one page or at least the first paragraphs of them then I'm going to have to move to a different platform anyway.

    ReplyDelete
  119. Yes, like Judy Abbott, I've been waiting for 7 hours for the HOSTED BY BLOGGER to appear, and it still has not appeared, any suggestions?

    Thanks
    Mark

    ReplyDelete
  120. @Rick

    I also have migrated a password-protected blog and now it no longer requires a user name and password. I definitely need this remedied.

    ReplyDelete
  121. Success!

    @Mark it took all night for Hosted by Blogger to appear for me.

    It didn't work on the first go, but I hit migrate a second time, and got a "moved successfully" message. I always had trouble publishing to FTP, anyway... I usually had to try a couple of times to get a post to take.

    The blog redirects in 30 seconds (that seems a long time): all the pages seem to redirect as they should; old posts, archive links, and labels all redirect in 30 seconds.

    There is a post at the top of my new blog (and old) with a message saying the blog has moved. This seems a redundant message for people landing on the right page - I assume it's safe to remove the post from the new blog while leaving it as the last post on the old blog?

    I began to move another blog several weeks ago by hand. It's already publishing at the new location. Can it be moved back to FTP so that I can use the migration tool? because the only other option I seem to have is to redirect ALL the posts, labels, and archives by hand - which would take forever. Are there instructions outlining the process of backing up new blog, switching back to FTP, migrating, and then re-applying the new blog style?

    @Rick thanks for keeping on top of all these questions. It's unfortunate this had to happen. seems to be creating a lot of extra work for people.

    TIP if you have any navigation on your blog, like links to the blog as a home page, or links to top pages, etc. - any links you made in your HTML template, you're going to want to update those first, because the migration tool won't do that. So the Navigation bar on my old blog links into the old blog. No one is going to sit in front of a site for 30 seconds waiting for it to redirect - they'll likely click something. Make sure those links point to your new location or they'll be waiting another 30 seconds.

    ReplyDelete
  122. @ Mark Argentino
    I don't work for Blogger, but I know that some hosting companies are very slow to update CNAME records (Earthlink only update theirs twice a day at 3PM and 11PM Eastern Time). You can check the status of your CNAME record at http://www.google.com/support/a/bin/answer.py?hl=en&answer=47283. Scroll down to "Check the status of your CNAME record" and enter the subdomain name you created.

    ReplyDelete
  123. @Rick

    What do I need to do with my URL feeds on Feedburner? I wrote a test post on the newly migrated blog; but, it does not appear on Feedburner.

    Therefore, isn't the sentence in the "This blog has moved" post asking feed subscribers to update their feed subscriptions pointing to the wrong URL?

    ReplyDelete
  124. Waiting to access the migrationtool as my blog is not considered ftp as I started the process... Waiting to hear about that.

    In the mean time, we've got a feed from the blog posted on the home page of a web site. I updated the dns so now the blog is not ftp. I need to update this feed to the web site so the content of the blog on the new url shows up on the home page. Is there documentation on how to do this somewhere? I've not found any yet. I need the URL to be the actual atom feed. Where can I find this?

    ReplyDelete
  125. Someone who's done this already please help me out: If I click "Start migration now," am I committed to completion -- and do I have to migrate all FTP blogs in the same session?

    Probably a stupid question, but I'm afraid to click to find out. I'm not ready to migrate all blogs.

    ReplyDelete
  126. @Michael

    You can migrate your blogs individually. Take your time with it because many of us still have questions regarding the blogs we've already migrated.

    ReplyDelete
  127. @Kris: Thank god. I have several, each with its own little quirks.

    On the positive side, this may be the push I needed to migrate from the old-style templates for good. I've just discovered that the new Blogger has several new features I could take advantage of.

    Another question for anybody: Once the blog is migrated, does anybody know an easy way to do a global search and replace to fix up internal (post-to-post) links, once migrated? Links in the template I don't mind fixing by hand, but links within post bodies are a big issue. If I could even just do the search and get a list, it would help.

    ReplyDelete
  128. @Michael

    One of my concerns with the blogs I've already migrated is, apparently, I cannot use my old HTML in the new Layout set up. I like some of the new features available in Blogger while I don't like some apparent limitations.

    ReplyDelete
  129. @Kris, I grok. But I've pretty much decided to live with the limitations, in favor of adopting a new, clean, simple layout based on denim. If I were in the business of commercial Web design, of course, it would be a different matter.

    I do wish they had a supported 3-col layout.

    ReplyDelete
  130. @Mark @Rick

    The CNAME and DNS updates worked overnight for me too.

    However, the FTP is a total bust. I have tried transferring the extracted zip files to my old blog subdomain directory and the 'new' blog subdomain directory (although I thought the whole point of migration was to have this data on Google's servers), but neither registered as successful after 12 hours (how long should one wait for this to work???). How is one to get to the next step?

    I wanted this done over the weekend because this was when I had the time to do this. But Monday has come and I am blogless. I have two blogs stuck in partial migrations at the FTP step and a third which is totally inaccessible but which was never migrated (presumably because my master DNS are pointing at Google and no longer at my ISP where the non-migrated blog resides.

    So - questions

    [1] When adding the Google DNS's we are told to do it for the 'master'? eg. www.example.com. But if you have a regular website at www.example.com and a blog at www.blog.example.com then presumably the Google DNS's are only done for the blog subdomain?
    [2] For me to get [1] to work I replaced my server's DNS with the one for Google - but I would like to know in doing this have I effectively disabled the FTP step because my server's DNS are no longer to be found to complete this step? What is the FTP step of the Migration tool calling???
    [3] To correct [2] can I add back my server DNS's? This doesn't fix the fact I am locked into a manual FTP which fails to allow me move to the next step. What will adding back my DNS too given my blog is already (partially??) hosted on Google?
    [4] Extending this thought again, will the transfer work if I only set the subdomain DNS's to Google's and leave the 'master' with my ISP DNS?
    [5] Are we going to be able to restart the migration tool?
    [6] If we are allowed restart the migration tool will this mean having to create another subdomain (I'm running out of good names to use)
    [7] What will all this blog downtime do to my Google search ranking?

    cont..

    ReplyDelete
  131. [8] Why is there no tech support over the first weekend of the Migration tool launch - the time most likely people are going to try to do this?
    [9] Why hasn't help focused on the steps which can go wrong rather than the everything is golden approach
    [10] The Migration Tool has been poorly designed; it is assumed FTP's know about CNAME and A designation changes but there is nothing in this step to suggest anything *has* to be done. You could be waiting for the "Hosted by Blogger" to appear to the cows come home *unless* you click a link to navigate away from the migration tool to find out what you have to do to complete the step!!! That's not typical wizard behaviour
    [11] The next step is worse. If automatic FTP doesn't work - Tough; here's your Zip and no instructions what to do next! Not even a link out to tell you what to do with the Zip file. The latter would have been bad enough, but nothing at all is even worse.

    In the design of this tool did Google reach out to any FTP account holder and work with them to make this tool easy to use? The answer to this last question appears to be a clear 'No' - it looks like testing was done internally with mocked up accounts. The migration tool fails to address any of the complexities of existing FTP accounts.

    I appreciate the time and effort @Rick has put into this and my rant is not directed at individuals but at how this migration protocol was put forward. There are people, like myself, who are eager to switch and get this done quickly - but I feel very much like a guinea pig. A guinea pig who would have been better served by Google reaching out to a core group of FTP account holders to get them volunteer their time and experience in making this migration tool simple and easy to use. I would have happily done this. It's part of my real-world job.

    The end result to this is that either people will move away from Google, or they will leave it all to the last minute to make the change. I am no tech wizard but I would like to think I have the ability to make what should have been a relatively straight forward process work.

    I have failed to do this.

    Declan

    ReplyDelete
  132. Thanks for this, Rick, I think that it's a well-done video and a well thought-through process. I appreciate the support. The one open question that I still have is how the use of the "rel=canonical" and http-refresh to redirect people from links pointing to content on the original domain to a new subdomain will affect search engine rankings. For example, if I had x thousand links pointing to Shore.com and those thousands of links are now being redirected to blog.shore.com and new links are now pointing at this subdomain, how will this affect how search engines view the shore.com domain as a valuable site? Will the subdomain and main domain be tallied up as one lump sum in PageRank?

    ReplyDelete
  133. First blog was a success, second got hung up at the "download a zip file of your blog" page. They were on the same FTP site, using the same template. One worked, the other didn't.

    ReplyDelete
  134. Hi Rick, sorry to bug you.

    @bevjackson Not ignoring you, had a family emergency. When we were last discussing this, you were getting doteasy to restore your uploaded files and images from a backup, and then setting up a CNAME subdomain that would point to those files. Have they set up the subdomain

    Okay, here's where we are. They set up my old
    blog directory (beverlyajackson.com) at this address public_html/www2/ Also, they found out that my images weren't all showing up because in this move, the Upper/lower case links didn't match (they never did) but NOW they didn't show in Blogger. I just have to go through and correct each link that is not identical to the directory at Doteasy. (I have no idea why they worked all these years the way they are??)]

    They also checked my Blogger account and I'm assuming they found nothing wrong with my setup.

    So, what remains is the question "Do I need to run this migration?" Or is my custom domain okay the way it is? Just not sure what that does. And if I need it?

    Thanks for your help. You've got quite a plateful. If I need to run migration, I don't want to fool with Beta and bug you anymore.

    I hope all is okay with family.

    Thanks again.

    ReplyDelete
  135. @Declan: I don't believe you have to move the files to Google's servers. They already have all your old posts in their database. The ZIP is a backup for safety sake.

    ReplyDelete
  136. @Store 44 Reps @Delan @others

    Yes, it took about 10 hours for the change of DNS CNAME to work and for HOSTED BY BLOGGER to appear, eureka!

    so now I started the update and so far it's 20 minutes into the update, I sure hope this works.

    I want to point out a couple of items that may help others, so they are not as frustrated as me.

    First off, I am hosted with Bluehost, I emailed the help and they were immediate with their help.

    I had sometime in the past created a DNS record for www.blog.mississauga4sale.com and for http://blog.mississauga4sale.com I tried to point the CName to ghs.google.com on both, but my CPanel would not allow it. I was worried that if the DNS only pointed to ghs.google.com for www.blog.mississauga4sale.com and not http://blog.mississauga4sale.com that I might have a problem with the migration. So I deleted both DNS entries for my blog this morning and created a new DNS entry for only http://blog.mississauga4sale.com with CNAME ghs.google.com It took about 10 hours for HOSTED BY BLOGGER to appear in the migration window.

    My blog has been active via ftp since about 2005 and I have just over 1100 posts, so I'll update regarding how long it takes for the migration process to finish, I have no idea how long it will take.

    Again, thanks to everyone for their help with this and to Rick for his great tutorial, FAQ's and advice.

    I know that some people are complaining about shutting down ftp, but if Google is spending a dis-proportionate amount of time and resources on maintenance of ftp then it makes business sense to cancel the ftp service.

    I have received great service from Rick and Google considering this is a free service to us!

    All the Best!
    Mark

    ReplyDelete
  137. Holly smokes, I just went back and checked the progress and I had the message "Update complete!" yippee!!

    It took less than 1/2 hour to migrate for about 1100 blog posts.

    As well, the verification returned: Finish Verifying... Verification successful, blog migration is complete!

    I did a test post and a few other things and everything is working fine, yippee!

    No more stress, no more worries, just more blogging!

    You can check out my new blog at http://blog.mississauga4sale.com

    All the Best!
    Mark :-))

    ReplyDelete
  138. I've tranfered my blog to a blogspot address and still wanted to use FTP publishing to my old address in the meantime, but this was after I hit "start migration process". Now, I can't get the template to publish because I keep getting "Publishing your blog is taking longer than expected. To continue waiting for it to finish, click here" error.

    I've been trying all day to get the thing to publish. Any suggestions?

    ReplyDelete
  139. @Mark: Congratulations! "We who are about to migrate salute thee," as the Roman soldiers used to say.

    ReplyDelete
  140. (Apologies for the lengthy delay today; as noted below, family emergency earlier in the weekend, then today was my son's 10th birthday. Should be caught up on comments now.)

    @Mark: Some registrars insert the '.' in for you; others require you to enter it. If CPanel is not allowing you to insert it, it's possible your registrar is inserting it on your behalf. If after typing it in it's not working, contact your registrar for guidance. It sounds like the cname may be for 'www.blog' instead of 'blog', which isn't quite right (it should be 'blog' if you want blog.yourdomain.com). Confirm that the CNAME is set up properly and double-check how your registrar prefers things.

    @Yoel: We will allow migration restarts this week - either by us or within the tool. Keep an eye on the migration dashboard. That said, if you've already migrated to the blogspot address, you can switch from there to a custom domain. Your FTP blog redirects to Blogspot, and Blogspot will redirect everything to your custom domain.

    @Declan: The FTP republish is republishing to your existing FTP blog, inserting redirects to your new URL. You shouldn't be FTP'ing anything to the new subdomain - that is what you're supposed to point to our servers. Thanks for reporting in the spreadsheet, I'm going through the last of those now and will verify status with every report

    @Dr. Effingpot: 1. Yes. 2. The FTP blog files should not be deleted, as they are what contain the redirects to the new URLs. 3. The new posts are on our servers. 4. You're correct, the A Records are required only when setting up a 'naked' domain, which a subdomain is not. 5. Image issues are probably related to the A record, if you removed hthe A records pointing to us that would have fixed the 404s on images. 6. There's no way to redirect feeds (short of using .htaccess on Apache servers, which is not guaranteed to work on all servers, so we instead chose to post a final post to the 'old' blog (including the feed) to tell prior subscribers to update their feed URL. 7. Any comment issues will take just a few hours to resolve (you'll be able to resolve them from the moderation panel).

    @Judy Abbott: it should be relatively quick. But I'll check to see what (if anything) would be holding that up.

    ReplyDelete
  141. @Dan Richter: Can you share a URL where you're seeing this? What should be happening?

    @Dean: Ah, got it. we'll have more news about better support for classic templates and auto-pagination in short order. If you upgrade to Layouts, you'll be able to use the 'older posts' / 'new posts' navigation options so that users can navigate through all posts.

    @Kris Gardner: Go to settings | permissions and restrict access. We allow you to restrict access on an individual basis. For FeedBurner, go to FeedBurner and edit your source feed URL to point at the new URL. What HTML can't you use w/Layouts? There shouldn't be any issues moving to Layouts that concern HTML mark-up.

    @Store 44 Reps: Yes, you can delete the post from your Blogger Dashboard; it'll remove it from the 'new' blog while keeping it on the FTP blog.

    @Michael: We'll have a big announcement that'll address any concerns you have about multi-column layouts. Keep an eye on Blogger Buzz for details. (Real soon.)

    @Declan: 1. Yes, only point subdomains to ghs.google.com if you host non-blog content at www.yourdomain.com. 2. (should be moot given answer to 1.) 3. yes. 4. yes. 5. yes, this week. 6. no, you'll be able to use existing choices. 7. nothing. 8. I was due to be support, and had a family emergency (child broke a bone). Really sorry - needless to say, completely unforeseen. 9. We are focusing on addressing those issues, engineers have written a number of tweaks to the tool over the weekend that will be live in production by tomorrow. 10. The migration tool indicates - in bold - that the next step is to create a cname. We recognize this is a challenge, but so far most of what we've seen is that most have made it past this step without issue. 11. Appreciate the feedback.

    @John Blossom: You're welcome! Google will interpret rel=canonical links as authoritative, and transfer any pagerank earned by the 'old' URLs and transfer them to the 'new' URLs.

    @bevjackson: You look to be all set. Images are showing, so no need to do any migration - you're done! Thanks for the concern - my son broke a bone, is holding up. We see the surgeon tomorrow to find out if he needs any surgery or just a cast.

    ReplyDelete
  142. Hello,
    I have used the migration tool successfully and the redirect works as well.

    So far so good. Only thing is none of the images show up and I read the point about the missing files host which I used. However still no images. Any advice?
    Peter

    ReplyDelete
  143. @ Rick
    Hosted By Blogger sign not appear yet. Were you able to check? I have 4 more blogs to migrate and am very worried:(

    ReplyDelete
  144. aiuto! traduzioni per gli utenti italiani????????

    ReplyDelete
  145. Probably I am just going to hire a programmer for like $15 to move my blog to wordpress - there are instructions to do this at:
    http://www.mamablogga.com/the-ultimate-guide-to-migrating-from-blogger-to-wordpress/

    Apart from issues to do this, blogger has many other issues. Now it's the PREVIEW thing too which displays error.

    Karl

    ReplyDelete
  146. @Rick thanks for the replies - just a few final points of clarification.

    1 - Can I delete the old FTP files or not? IE will old posts disappear if I do that or not - I hear you on the redirects but I don't care about them. (When you say redirects, I imagine that means if someone links to an old post it will redirect to the new hosted version of the same post right?)

    2 - On the RSS Feed - again I don't care about the old posts being in a feed, just the new ones. Where do my readers get a NEW feed? Following the instruction the migration tool posted they only see the old posts and no updated new ones.
    Thanks
    Mike

    ReplyDelete
  147. Oh my COMMENTS have been migrate 3 days now and the bug still exists. When you SELECT then approve (or reject) the comment, it says NO COMMENT SELECTED.
    But it was selected so this seems to be a bug.
    Not major but one I'd like to correct.
    ta
    Mike

    ReplyDelete
  148. Half my blogs are for members only - I use a membership software and password protect the blog folders - I have a custom domain + the first blog is already set. Is there any way to protect my content in a similar way once I no longer use FTP?

    PS: setting the blog to private with the blogger "permissions" feature is not an option because I have hundreds of members + the access is fully automatized via my membership system.

    ReplyDelete
  149. @Rick -- I am hoping to hear from you or someone else today about my inability to export my blog and therefore migrate. If no fix yet please let me know the state of play.

    http://www.nipissingu.ca/department/history/muhlberger/blog.htm

    Best of luck with the broken bone.

    ReplyDelete
  150. Hello Rick & team, if my blog is currently widget.com, and will publish as blog.widget.com after the migration, can you advise if I should do the following?

    (1)widget.com CNAME set to ---->ghs.google.com.
    (2)www.widget.com CNAME set to ---->ghs.google.com.
    (3)blog.widget.com CNAME set to ---->ghs.google.com.

    I have no need to touch A RECORD/A NAME, right? Why am I still seeing errors?

    Thanks a mill!

    ReplyDelete
  151. @Rick

    Hi,

    we have our Blog at www.anc-news.de/newswire (the blog is the index.htm) for many years. We dont want to send our customers a new url like www.newswire.anc-news.de - can i make a "invisible redirect" ? So the User can still go to www.anc-news.de/newswire without a note like "we have moved to...." ?

    thanks and greetings from germany,
    Rene

    PS. Its a very bad news the bloggers ftp-support is lost !

    ReplyDelete
  152. @Rick
    So that I got HOSTED BY BLOGGER sign but now another problem:

    the redirection post appears on the new address (kitap.realfiesta.com) and NOT the old FTP blog (realfiesta.com/bookclub.htm)

    and now I will not be able to post to old FTP blog. how am i suppose to redirect people from old blog address to new one?

    the same thing goes for my second blog:

    http://www.realfiesta.com/alpacino.htm MIGRATED to http://pacino.realfiesta.com
    I can post to new address. However the redirection message appears on the NEW address blog and NOT on the old one. HOW on earth I will post to old FTP blog to redirect my followers?

    I am VERY dissappointed at this migrate tool.

    ReplyDelete
  153. To capnchaos: I think you're on the right track. We have 300 pages happily residing in our ftp system and damned if we want to risk screwing all those up.

    Remember: technology is meant to make life easier, not harder.

    So, as a test, we downloaded the ftp version of one of our lesser blogs that we had also transferred to a new blogger address. we stuck a notice on the ftp version directing readers to the new blogger address and new rss address.

    i figure if it works with snail mail when you move it may work on the net as well. We'll see. - Sam at prorev.com

    ReplyDelete
  154. So, it seems we users are again at the mercy of any Baldrick that "has a cunning plan". I have been a happy user since November 2001. No more.

    ReplyDelete
  155. After I did this I have noticed that now the "search this blog" gadget as well as the blogger search in the top section are no longer effective. Any reason as to why or how to correct it?

    ReplyDelete
  156. So.. they grow and become microsofts.
    This is BS, why and how should I trust blogger with my content ever again? First time clearly was a mistake, second time would be stupidity on my part.

    ReplyDelete
  157. Hi Karl!
    Is there any delay at the moment with the help section. I've filled up a form two days ago and I did not get any anwers (about my blog having migrated but not being able to publish anything..) THX! We keep the faith..

    ReplyDelete
  158. @Rick Klau
    Here's the URL I was talking about: http://www.danrichter.de/improblog/gedanken.html

    ReplyDelete
  159. Question: My current ftp blog is published to a subdirectory of my domain. (domain.com/blog)

    How can I KEEP this url and still perform the update?

    ReplyDelete
  160. @Rick

    I think I posted my resolution to blog migration to a different post than this one. I don't know if you want to relocate the comment here to give it context to what I had experienced earlier?

    Suffice to say - I was able to migrate my blogs in the end!

    Thanks,
    Declan

    ReplyDelete
  161. My blog seems to be stuck at the "preparing for migration." It's been 24 hours and it has not moved beyond this point.

    ReplyDelete
  162. Corporate America strikes again! Thanks Google!

    ReplyDelete
  163. I made a solution that can let you keep your old domain name and old ftp solution... as is. If you want to try it. http://digg.com/d31KvPY

    ReplyDelete
  164. @Rick Any update on the possible DNS issue? I am still having problems seeing blog.backyarddiyguy.com consistently. Occasionally it will return the pages as it should, but most of the time, I get the Test / Apache successful installation page when trying to view the blog home page, and 404 errors when trying to view any specific blog entry.

    ReplyDelete
  165. Rick

    We used your tool to move all of our blogs out of ftp to addresses with .blogspot at the end. Everything went over fine and looked fine. Today I went in to modify one of the templates and it will not update. I get this message: "We're sorry, but we were unable to complete your request.
    The following errors were found:
    securityToken: Your request could not be processed. Please try again. "

    What do I need to do?

    ReplyDelete
  166. Rick
    Also, I also cleared the cache and cookies and I still get the securityToken error that will not post changes to the site.

    ReplyDelete
  167. This totally worked for me! and I can still keep my own hosting (which I need for files now and then).

    http://www.posttwo.com/blogger-ftp.asp

    anyone know why this wouldnt be a preferred method?

    ReplyDelete
  168. @Rick

    Okay - maybe spoke too soon!

    Markets.fallondpicks.com works
    www.markets.fallondpicks.com doesn't

    I thought adding [A] DNS entries for the 'www' would work but it returns a Google not found 404 error.

    Anyone else having this issue were the migration is reported successful?

    Thanks,
    Declan

    ReplyDelete
  169. @Rick
    the re-direct on this page:
    http://www.thehrr.com/HRR_Fans_blog/index.shtml
    just goes back to the same page

    Regarding the HTML code, on this page:
    http://fansblog.thehrr.com/, I have a share widget / gadget in each post.

    When I changed to custom layout, it disappeared; therefore, I tried to copy the code into the HTML layout to appear in each post. It didn't work. I tried adding the "Sociable" gadget; but, all that did was post at the top of the page instead of in each post.

    ReplyDelete
  170. @Declan: It shouldn't work. 'www.markets.fallondpicks.com' would be a subdomain of a subdomain.

    ReplyDelete
  171. Labels - my migration kind of worked but now if I click on my LABELS which are listed on the right of my blog it only lists those blog entries from the old FTP blog.
    This is because it links to my old site/blog/label/whatever.

    How do I recode my label links to INCLUDE the new posts please?
    thanks
    Mike

    ReplyDelete
  172. OK, I am _hugely confused_. I have a domain and hosting and blogger has always FTP'd the blog to the index file on that webspace. In addition to the index file there are 1500 more pages of html, all of which link back to the home page and the blog.

    All I want to do is to keep this situation exactly the same, but I have no idea whatsoever how to do it! The blog is already broken, and I have no access to any of my other pages other than the blog homepage (which can't see my css file).

    Please help!

    ReplyDelete
  173. @Dr Effingpot: If you switch over to layout-style template, your problem is solved rather easily, because there is a widget that can display all or some of your label links. If you continue to use the same template, you'll have to edit all the URLS in that section. The new format for each labelname will look something like this:
    http://blog.domain.com/search/label/labelname.

    ReplyDelete
  174. @Michael: Thanks that worked a treat - I just edited the template. The categories hardly ever change so I'll stay put the way it is.

    ReplyDelete
  175. Quick question: I understand the deadline is May 1 . . . and I'm working on getting a subdomain (but I must upgrade my web hosting plan). In meantime I'm trying to upload (FTP) my blog but it's not working. Can't we upload until May 1?

    ReplyDelete
  176. FTP users: I noticed that all my FTP blogs stopped accepting posts a few months back. I finally figured out (looking at the provider's help file) that my provider wanted a different username format, that included '@domain.com'. Before, I could just have 'michael' as the username (see Publish settings). Now it must be 'michael@domain.com'. When I made this change in all the Publishing settings pages in Blogger, everything started working like a champ again.

    I also post to another FTP blog on a different provider. They didn't make a change. So this change may apply to some providers and not others.

    ReplyDelete
  177. @Rick

    My migration process is still stuck on "Preparing blog for migration." What can I do to move forward?

    ReplyDelete
  178. @Michael @Rick

    Thanks - is there anything I can do to get www.markets.fallondpicks.com to work? Or is this a Google side fix?

    (Same for www.tradingjobs.fallondpicks.com)

    Declan

    ReplyDelete
  179. @ Rick

    My images still don't show on the blog and my blog doesn't look so good without pictures. I enabled the missing file host but I have the feeling that no images have been transferred to it. Thanks for your attention.

    ReplyDelete
  180. Is there any way to maintain the existing RSS feed? If not, is there a way to have that feed's URL automatically redirect to the new feed?

    ReplyDelete
  181. Hi all. We have changed (hopefully improved) how we're handling issue reports. Previously we directed you to a spreadsheet, but we found that created problems with follow-ups, and also made it harder for other users to see previously reported issues that might be related to their issues.

    We've been exploring a better approach to user support, and we're going to put our approach into action to manage the FTP migration. Starting now, please go here to report any issues:

    https://code.google.com/p/blogger-ftp-migration-tracker/issues/entry

    This will create an "issue", which we will then update as we have additional information. Each update will produce an e-mail to you (and anyone else who clicks the star button) with additional info.

    Prior reports have been ported to the system, and we are now in the process of updating those reports. (If you reported an issue, search for your URL here: https://code.google.com/p/blogger-ftp-migration-tracker/issues/list -- updates will be posted throughout the evening.)

    ReplyDelete
  182. ftp publish isn't working at all.
    and i can't even preview my template.
    congratulations google. you shat the bed.
    completely.

    ReplyDelete
  183. If I just want to stop adding to my blog, is there any reason I can't just leave it where it is? I understand I won't be able to use blogger to add to it, but of course I can always tweak things manually using any other ftp client to my host computer. If I don't use the migration tool, will google indexing, etc, remain for the existing blog in the existing location?
    Thanks,
    Julia

    ReplyDelete
  184. I just googled "complete fiasco" and this blog was the #1 result.

    Keep FTP the way it was.

    ReplyDelete
  185. @Julia Kay: That's a perfectly acceptable approach.

    ReplyDelete
  186. My domain is resolving as follows:

    ping www.othercrap.com
    Pinging ghs.google.com.othercrap.com [64.38.199.204]

    ping othercrap.com
    Pinging othercrap.com [216.239.34.21]

    ping image.othercrap.com
    Pinging image.othercrap.com [64.38.199.204]

    But my blog isn't working. "The DNS record for your domain is not set up correctly yet." What do I need to change?

    ReplyDelete
  187. @Uncle Scoopy: when you ping www.othercrap.com, it should resolve to ghs.google.com, not ghs.google.com.othercrap.com. The CNAME for www needs to be fixed to resolve to ghs.google.com.

    ReplyDelete
  188. Thanks for the quick reply.
    It's fortunate for me that I was planning on winding up one blog (after posting every day for three years) and starting a new one so I won't have to go through what looks like an excruciating process. Perhaps needless to say, the new blog will be over at Wordpress or elsewhere....

    ReplyDelete
  189. Note: Comments are closed on this post. Please direct general questions to the FAQ page, and specific problems with the migration tool to the issue tracker. More details about support for the FTP migration are here.

    ReplyDelete