Skip links

Join 2,509 other smart freelancers!

Sign up to learn how to keep your skills up to date on the tech that matters most and confidently sell your skills to a growing customer base.
I will never spam you. You can unsubscribe at any time.

Reader Interactions


  1. Basically the same process here. I had actually been using Desktop Server for a little while before I discovered the Blueprint feature. My mind was blown. It’s incredibly helpful, especially if you have a plugin, or group of plugins, that you always include with a site that require licensing (i.e. Gravity Forms).

  2. Been using DesktopServer since the beginning of the year… I’ve deployed from local to live, I’ve set up a local from a live site to tinker and then manually pushed out changes. I just yesterday set up a site on Flywheel and they moved it all for me, that was fantastic! Should be launching very soon.

    • Glad to hear you like their local to live process! I’m hosting this site with Flywheel and I love it. So easy to set up dev environments and pass billing to a client, but I wish they had a playground, so to speak, where I could play on a live environment, but not necessarily transfer that to a client at some point.

  3. Hi, Carrie — first time commenter.
    Super helpful post as I’m just getting started. Also a MAMP user, but intend to play around with ServerPress to see what it’s all about. I do use ManageWP, but have yet to try the cloning feature.
    Thanks so much for the help! Looking forward to the office hours!

  4. Hey again Carrie!

    Thanks for the mention here as well. I just finished reading the article you posted a couple of days ago, so I’ll just say thanks again and if anyone has any questions about DesktopServer, please feel free to ask!

  5. I build all client sites live on a test domain, then use BackupBuddy to move them to the client’s server (assuming it’s a brand new site). I’ve been considering ServerPress but for right now, I see no reason to change up my workflow since it works well. PluginBot is a great tool for live builds since I can install all my preferred plugins at once.

    • I’ve done basically the same thing as you, Andrea, but using ManageWP instead of backupbuddy and just manually going through the migration process in the rare instance it doesn’t work (I encourage clients to host on my server, and as long as the server is quick enough, that has seemed to work even on larger sites).

      I’m probably going to switch over to DesktopServer, though, after watching a few of their demo videos. Actually found this blog entry while looking around for DesktopServer coupon codes. Main advantage for me would be that on a local server it’s just so much faster to refresh, change settings, etc.

      Glad to see other people looking at this sort of a tool, too. I feel like a cheater when I use some of these one-click solutions for things that I know how to do, but just don’t enjoy doing.

  6. THANK YOU!!! It’s like Christmas all over again! I’ve have a major need for a better work flow – just read the previous post too – double the goodness!! 🙂

  7. Thanks for sharing this, my friend. I love (honest) workflow posts! I recently started using Desktop Server as well, and am loving what I see so far (but still have a long ways to go, I think). You got me hooked on ManageWP a year ago, but I’ve had similar issues with cloning so will check out the other option now. So thanks!

  8. Hi Carrie… I’m sort of a WP newbie started a few months back. But, i am a computer tech by trade. Just thought I would share that haven’t learned all the tricks people talk about but I really do appreciate all the help I get around here.. especially with all the God loving people using Genesis.

    I use Siteground and have used another host just prior and no comparison. I like SG due to the fact it is really fast, support is great when I need it and they have a staging feature that I love.. I can stage up to 10 sites and push them to live in a matter of seconds. Takes about 30 seconds each way. I still have a ton to learn and love your dedication to help people like myself. Thanks for all you do.

    Siteground also allows me to refer someone and they can get a basily a year free after they pay for only a month. I’m not here to post the affiliate link but if anyone would like that deal they can certainly request it from me and I will send. I actually have their Geek acct. and could not be happier. I have about 10 sites I and working on and finished up 3 so far.

  9. Hey Carrie your post is most timely as just today I’ve invested in Serverpress and am still basking in the glow of its awesomeness.

    Having previously worked with MAMP Serverpress is definitely a great way forward and although I’m only stepping out with Coda, the integration with it is superb.

  10. This is awesome. You’ve opened up the curtain to let us see inside all things Awesome Carrie! That is super cool and very helpful. We probably need to discuss workflows more so that we all can learn from one another and improve. I’m definitely sharing with my team!


    • Thanks for bring up VVV! I’ve been a little intimidated to set it up, but am curious about it. Can you share how it’s used for deploying local to live sites or is it excel just as a local dev setup?

    • Better is a subjective term. Note that Vagrant out of the box, doesn’t have copy or blueprint features. Keep in mind that DesktopServer runs natively on your computer without a Virtual Machine. There is no “booting” up, virtual hard drive, virtual network drivers, file system transfers, or anything like that. It uses less memory, less CPU, and runs faster than Vagrant. It works on your local computer just like “Word” or “Excel” and is built specifically for your computer’s microprocessor and operating system. You can edit your files directly in your favorite editor without having to mount a virtual file system, etc.

      Both DesktopServer and Vagrant are open source. I think what you mean is that Vagrant is “free-er” as in “free beer”, “I don’t have to pay for anything” for access vs SaaS, updates, or support. Not to be confused with “free” open source which pertains to copyright (or “copyleft” as us FOSS developers like to call it).

      That being said, Vagrant has some bonuses if you have the extra hardware to run it. You might not be creating a site in under 5 seconds like you can on the latest Macbook Air with DesktopServer, but once you do boot up a Vagrant, you can customize it to look more like your hosting provider’s hardware. That can be advantages if you want a more seamless environment (provided your hosting provider reveals their internal specs. or you do the research to find out what those are).

    • I use VVV for much of my development, but also use DesktopServer alongside it. They hit two different markets if you ask me, and actually work well for me side-by-side. Vagrant is amazing at providing a full server environment that can mimic your live environment for fuller testing and VVV specifically gives you a great WP environment. DS brings an unmatched ease-of-use that many designers and beginning developers will prefer and has some pretty sweet features with their deploy method and blueprints.

      I’d hesitate to say that one is really “better” over the other. It’s all a matter of how you develop and what your needs are.

  11. Great post, Carrie, as usual! I’ve been using Migrate WP Pro, DesktopServer (Loves it), along with Git and DeployHQ. Although, Siteground and WP Engine’s Git push capability are pretty amazing.

    I’m intrigued by setting up Vagrant and Grunt, but not seeing too enough benefits to abandon what I have. Though, with that line of logic I may be going the way of the WebKing ( sooner than later.

  12. Oh, how I struggle with workflow. Thanks for sharing yours. The hardest part is pushing changes to an existing site. I wish it were more straightforward. You can set up Git and deploy changes to your files, but then there is still that pesky database! I wish that WordPress would enhance its native export/import to include everything (menus, widgets, etc). I’m not sure why they don’t or if there are any plans to in the future, but it sure is a pinch point in the process. I also struggle with the idea of writing over the entire db when you only want to update certain things. I haven’t tried WP Migrate DB Pro yet, but I know I need to, as it seems to be the best solution as of now.

  13. Great post! Just found your site. I’m new to Genesis and really love it.

    Here’s what I do…

    New site:

    – create on dev domain on my own hosting acct
    – once complete, clone entire site using WP Twin by Rapid Crush software, but Backup Buddy would probably work well, too. I love WP Twin as it copies the db, changes all urls, never times out.
    – deploy with WP Twin on live url. WP Twin deploys is seconds.

    Existing site:

    – clone with WP Twin and deploy to a dev domain
    – make changes and reclone
    – wipe live WP install, create a fresh install of WP and deploy cloned update.

  14. A few nuggets (especially in the comments!) that I haven’t heard of. I want to start playing with Desktop Server – I need a deploy to live solution that works better than the old FTP one 😉

    My biggest problem comes with deploying to a live site that has its own content on it. Depending on what is on the old site – if all they want to keep is the posts/postmeta – I might pull the database and then merge the two SQL backups (from development and live) before dropping all the tables in the database and re-importing the new, merged, one (of course I make sure to keep a full backup in case I mess up royally, which never happens <– , 😀

    Great post – I love seeing what others are doing!

  15. Great post, thank you for sharing! You made me excited about Desktopserver and now I see there’s a coupon code possible. Does anyone know a working coupon code?

    • Thanks Matt! Not sure of a coupon for DS (the one I mention is for Migrate DB Pro). I’d suggest starting with the free version of DS – it’s still a really awesome piece of software. The primary capability of the paid version is deployment to live server.


      • Another huge benefit of the paid version is the ability to create your own blueprints.

        You can use blueprints to create a site in the free version but you’re stuck with the stock blueprints.

        Just my two cents 🙂

        • Austin, thanks for the comment. Actually, you can create a blueprint and put it in your xampplite/blueprints directory and it will show up in the dropdown. The main difference is that the blueprint you create will not have the plugins activated, whereas with the paid version, you can use the “export” feature which has all of your plugin registration information along with whether or not it was activated.

          Hope that clears things up! 🙂

  16. We don’t do much maintenance to sites we didn’t create.

    And we don’t like to develop locally, but for clients who are first-time web owners or established clients that are getting a new domain but have not decided on it yet, we often develop the client site on a local iMac ( via XAMPP) or on one of our domains we use for testing on our dedicated server (at We then migrate it to the client’s server and domain.

    Over the years, we find that the WP Codex migration instructions work just fine and without any added expense. In the past we’ve been bitten on our “bottoms” with 3rd party plugin tools and pay-per-month services.

    Do understand: I’m sure that the services and products mentioned in the comments here are fine… but we like being in as much control as we can, to say nothing about the costs involved.

    The really big ‘gotcha’ in migrating WP sites from a development platform to a client’s production domain is the fact that WP (for some dumb reason I’ll never understand) decided to serialize the site URL in some of its tables.

    Lots of people will do an SQL dump of the database to plain text and use a text editor to search and replace… i.e –> Well, because of string lengths and other issue with serialized data, that method can also bite you on the “bottom.”

    So, what is the answer? Simple. There is a terrific free tool that has never failed to work for us.

    We dump the development MySQL file and load it to the client’s site (both via phpMyAdmin) and then upload this little PHP program and run it with the database’s user, passwords, DB-name, sever info (same stuff in wp-config.)

    You can read about and download the program here;

    My guess is that there is code similar to to what is in the above in the routines by the various services and plugins that seek to make migration easier.

    If you follow the WP Codex methodology ( and I can’t believe that professional developers would have any trouble doing so) AND use the little PHP program by InterConnect/It you will get flawless results and won’t have to pay 3rd party costs.

    Yes, it takes us a tad more time but we get to control the process which is one way we protect our “bottom.”

    Hope this is of value to someone.

    (And Carrie, we love your blog. While you are a strong supporter of WP ( and Genesis, which is our weapon of choice) you are also one of the few writers in the genre not afraid to be critical of WP or some of the products (themes, plugins, services) when criticism is warranted. You’re the best of the best!)

    • Hey Al,
      Great points you bring up – you’re right that serialized data has always been the biggest PITB (Pain in the Bottom) when it comes to moving sites around. Thanks for sending the Interconnect link – I hadn’t seen that.


  17. I start everything with a git repo in Beanstalk. I clone that locally and build my site, committing along the way. (Beanstalk automatically deploys to my staging server when I do a local commit and push). Once I’m ready for the client to see the site, I use Sequel Pro to export my local db and import into the staging server’s db and replace the appropriate URL strings.

    And of course I have this whole process automated down to a few clicks using Alfred. 😉

  18. Hi Carrie,

    I do have a problem too with Pushing changes from development site to an existing live site. I have not been able to find a solution that would make all changes, uploading 100% secure.

    I believe this is a niche in WordPress applications and whoever make a software to make this process smooth will make a lot on money 🙂


    • Yes – that is a big problem for a lot of folks! Keep your eyes on DesktopServer – rumor is their next major release will improve the deployment feature to address this.

  19. Hi Carrie-

    I came across your site while looking for information about DesktopServer and other deployment methods. What I can’t find is a good way to handle https (SSL) situations. Do you (other anyone else “listening”) have any ideas? Testing e-commerce sites locally would be much more preferable than testing live. Even SiteGround’s staging prevents you for doing SSL teseting.

  20. So I did some more research last night and came across a product called WampDeveloperPro ( According to its specs and features list, it supports SSL (self-signed) and somehow allows you to install SSL certificates. Of course the problem here is, this is really “stretching” what I know how to do… not that that is a bad thing, but it’s hard to evaluate when learning the technology at the same time…

    So is ANYONE familiar with using this product?

  21. Hey Everyone,

    With regard to DesktopServer and its ability to do SSL, while you are correct that the current iteration dust not support it, Version 4.0 will make it possible. We are at the tail end of alpha testing right now and are just weeks away from the beta testing which we feel will be a short period (but as with all software, may be subject to change).

    I realize that does not solve your immediate need but it might help to know that it’s coming down the pike. 🙂

  22. Well Marc that was all of the “nudge” I needed – just purchased the premium version. I would be happy to help beta test the SSL feature if you’d like when the time comes.

  23. MigraDB Pro ? I mean, it takes 1 minutes to dump and move the DB from one server to another.

    The problem is not the DB but the Media Files,etc. Those things generated dynamically on the live site.

  24. I’m looking for a solution to push changes form dev to prod also. Seems to not existing yet. Thanks for your post!

  25. Hi Carrie, I just discovered WP Stagecoach ( which handles that last piece of the puzzle: merging changes from staging to live. They’re currently in beta and free at the moment so I’ve signed up to give it a whirl this month.

    If you have a chance to check it out, I’d be interested in getting your thoughts on WP Stagecoach.

  26. Hi Carrie,

    There certainly is a lot of love going around for Desktop Server! A lot of people I have been talking with at WordCamp London this weekend like it to. I think you’ve pushed me into giving it a spin. Here is what I do:

    I use MAMP Pro which makes it reasonably fast to set up local sites, with ‘proper’ urls: i.e. or whatever. I do have to create a database manually using the built in phpMyAdmin but this all takes less than 5 minutes. Add on the 5 minutes for the world famous WordPress install process and I am good to go in about 10 minutes all in. Not exactly light speed, but fast enough.

    I always start a new entry in 1Password for any new site too.

    I create a ‘one-size-fits-all’ wp-config file. I configure this to work with my local, staging and live servers. Set this once and I can then forget about it and get on with the ‘fun’ stuff. Here is an example of my wp-config:

    By setting the site url in the config means I don’t need to mess around with a find and replace in the WordPress database. If I add links or images as I develop I just give them relative urls instead of the full URL including domain name. i.e: becomes /my-new-link

    So when it comes to deploying the site. I used good ‘ole sftp and a phpMyAdmin export and import of the database. Not exactly cutting edge, but it’s tried and tested. 😉

  27. I tried the free Desktop server version and it kept crashing. It wouldn’t even start up the server for me. It worked for about 10 minutes, and then I started having problems and went back to Mamp. I’m experimenting right now, trying to find out an ideal work flow using Git, I guess we’ll see.

  28. Hi John,

    I’m sorry this is happening to you. I am sure that if you shot us an email, we’d be happy to help you troubleshoot. It should not be crashing every ten minutes. And, obviously, if it was a common occurrence, we’d be out of business!

  29. Curious to know if I need to go with Desktopserver Pro or not?

    We are looking to set up a system with WP on local but also have a Stash/Git repository and deploy to a cloud VM. Can I do this without desktop server limited? I’m not really sure what the ‘live deploy’ system is?

  30. Carrie, Thanks so much for this post! Your content and (teaching on Lynda) is legendary 🙂 I made the leap to DesktopServer after reading this, and the difference it’s made is day and night. Using the Widget Data Settings import and export app to migrate widget data but its still a bit fiddly, besides Migrate Pro wondered if you had any tips for preserving widget data when releasing to live site?

    • Thanks, Rich! If you’re using Migrate DB, that’ll include all of your widget settings! I’m sure there are other tools to do that (like the plugin you mentioned), but Migrate DB does such a good job I’ve got no reason to change. 🙂

  31. Hi Carrie. What do you do in the event of making changes to an already live site where the data on your local version is different to the data on the live version? Therefore a push/pull wouldn’t work as it would copy over either version. It’s more of a merge.

    In a real life situation, it’s when a client asks for new features but continues to edit the live site.

    • Hey Rob,
      That’s a major rub for everyone. I’d pull down a latest copy of the site, do any development locally, then copy the live site to a staging site (most managed WP hosts have this feature). At this point you’re working with the latest data, sans your new development. Push your new _files_ to staging site and integrate your updates. Of course, this is a PITA if your new development involves any database config. For most sites I work on, clients are not publishing content daily (or even weekly), so coordinating the effort is easier.

      You might keep an eye on this -> It’s from the guys over at Migrate DB Pro and looks like it could be a Christmas miracle.

  32. Yeah think everyone struggles with it… I keep asking everyone in the hope that someone has solved it. Yep the developer gave me a heads up about that… no timeframe of when it’s coming out though.


Leave a Reply