Title: Lifesaver Last modified: September 2, 2016 --- # Lifesaver * [fastasleep](https://wordpress.org/support/users/fastasleep/) * (@fastasleep) * [12 years, 3 months ago](https://wordpress.org/support/topic/lifesaver-26/) * The only way they could make Jetpack better is if it had a fully automated “Import Everything from WP.com” module that handled all your site content, followers, and stats. Getting content imported was a pain to say the least, but once that was done, Jetpack helps you replicate many if not all of the features that one may have been using on their WP.com site. Just contacted support to get the email followers transferred, and hopefully stats and anything else they can move as well. 🙂 Viewing 5 replies - 1 through 5 (of 5 total) * Plugin Contributor [Richard Archambault](https://wordpress.org/support/users/richardmtl/) * (@richardmtl) * [12 years, 3 months ago](https://wordpress.org/support/topic/lifesaver-26/#post-7828501) * Hi, thanks for the review! * Your idea is a very good one, I’ll pass that along to the developers. Just so you know, when you contact us to transfer your followers and stats, we make sure that everything is ok with your Jetpack connection and your site at the same time; for example, if there is any problem with the connection, we troubleshoot before moving the subscribers. Also, if we notice that you’re running older versions of Jetpack or WordPress we take the opportunity to tell you so. 🙂 * Lastly, for stats, transferring them can result in wonky stats if post IDs on the current site are different than what is on the WordPress.com site, which is why we don’t do that automatically either. We prefer to warn people about that prior to transferring stats. 🙂 * Thread Starter [fastasleep](https://wordpress.org/support/users/fastasleep/) * (@fastasleep) * [12 years, 3 months ago](https://wordpress.org/support/topic/lifesaver-26/#post-7828506) * That is a good point. I would assume then that doing a full export and import using the WP.com importer preserves post IDs? We did that, then for the couple weeks during which we were still fixing things up and integrating the blog etc, we were manually duplicating posts on both wp.com and our wp.org install for a handful of posts, so that when we turned on Site Forwarding, everything would still be in place. What happens then? 🙂 I suppose those posts might have the same ID if we didn’t do anything else differently, but not sure. * I think my main suggestion from the above then would be to integrate a robust WP.com importer for posts/pages and media. The standard WP.com importer is broken at best, it took me many many hours of trial and error and researching other peoples’ posts to find out I had to just refresh the browser over and over to get it to import the whole database, and then trying various plugins to finally get image *links* back to files.wordpress.com to link locally, etc. Not a process for the faint hearted. It’d be awesome if someone would fix that importer so it doesn’t just fail on a blank screen if you have a large site. 🙂 * OH and if there was some genius way of importing one’s WP.com settings so that Jetpack is configured to basically duplicate those features, that’d be awesome too. * Just thinking out loud after a long site migration process. 🙂 * Plugin Contributor [Richard Archambault](https://wordpress.org/support/users/richardmtl/) * (@richardmtl) * [12 years, 3 months ago](https://wordpress.org/support/topic/lifesaver-26/#post-7828516) * Hi! * > I suppose those posts might have the same ID if we didn’t do anything else > differently, but not sure. * For the imported posts, yes, they should have been the same. For the manually- duplicated posts, not necessarily so. * > The standard WP.com importer is broken at best, * Your import file must have been really massive, then, or your server has limits that were too low for the job to function properly. In any case, since you’re done, we won’t troubleshoot that any further, the important thing is it’s fixed! * > It’d be awesome if someone would fix that importer so it doesn’t just fail > on a blank screen if you have a large site. * I found a Trac ticket that I think is related: * [https://core.trac.wordpress.org/ticket/21859](https://core.trac.wordpress.org/ticket/21859) * Feel free to add to that or follow it, or create a brand new ticket if you think this one isn’t relevant. * > OH and if there was some genius way of importing one’s WP.com settings so that > Jetpack is configured to basically duplicate those features, that’d be awesome > too. * That’s an interesting idea; which setting should be imported, though? Which ones would be valuable enough and are enough of a hassle that they would merit a user installing and/or manipulating a new module in Jetpack? I’m not being sarcastic, by the way, this is a legitimate question. 🙂 I’d like to open a ticket about this but I’d need a bit more feedback from you about what would have made the process smoother for you. 🙂 * Thanks! * Thread Starter [fastasleep](https://wordpress.org/support/users/fastasleep/) * (@fastasleep) * [12 years, 2 months ago](https://wordpress.org/support/topic/lifesaver-26/#post-7828521) * The XML was 6.3MB. The problem arises when you have it import all of the media attachments (in this case, 2000-something images of varying sizes). That Trac ticket does sound related. Even if that part is fixed, while it imports and relinks the attachments to the posts (or should), it does not update links wrapping the images (inserted by WP’s media embedding/linking) which in this case all pointed back to files.wordpress.com. It was a combination of external image downloading, image link replacing, and good ol’ Search and Replace plugins that ended up fixing everything “good enough”. 🙂 * I guess what I was thinking was importing every admin setting which has an equivalent between wp.com and wp.org+jetpack — from permalink structure to reading/writing settings to thumbnail sizes and so forth to bridge the gap — but I realize that’s probably a bit tricky. I was just thinking out loud mostly. 🙂 I think the WP exporter/importer thing would be more universally useful to people as I ran into many, many threads with people solving for the same problem I had. * Thanks for listening! * Plugin Contributor [Richard Archambault](https://wordpress.org/support/users/richardmtl/) * (@richardmtl) * [12 years, 2 months ago](https://wordpress.org/support/topic/lifesaver-26/#post-7828524) * > The XML was 6.3MB. The problem arises when you have it import all of the media > attachments (in this case, 2000-something images of varying sizes). * Yeah, that would do it! That’s quite the import 🙂 * > I guess what I was thinking was importing every admin setting which has an > equivalent between wp.com and wp.org+jetpack * I can see that as being useful for some folks, but at the same time, people who go from WordPress.com to self-hosted often set things up differently, from what I’ve seen. They experiment with the settings, try new things, and so on. * I’m still intrigued by your idea, though. If you want to think about it a bit more and come back with a more refined suggestion for a Jetpack-based importer, I’m definitely all-ears still! Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘Lifesaver’ is closed to new replies. * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237) * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/) * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq) * [Support Threads](https://wordpress.org/support/plugin/jetpack/) * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/) * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/) * 5 replies * 2 participants * Last reply from: [Richard Archambault](https://wordpress.org/support/users/richardmtl/) * Last activity: [12 years, 2 months ago](https://wordpress.org/support/topic/lifesaver-26/#post-7828524)