PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Moving day - take your entries and move them to your new db

  1. This isn't a question, problem or bug. This is a BIG thank YOU to the Rocket Genius team for being awesome. It is because they are awesome that their product is awesome.

    Why the love? Well, I rarely get to post on here because:

    1. The Gravity Forms documentation is very thorough.
    2. The code is extremely well written - take the time to read it. It will talk to you.
    3. The handfull of times I've had a question, I've searched this very forum and found the answer.

    Today, I had a question. A big one. How can I copy entries on from my massively complex, multisite, multinetwork, multiserver environment to my sorta complicated, multisite, single server development environment.

    Chances are just about any question you can have has already been answered on here, several times. But what if you are running multiple layers of nginx that connect to isolated php-fpm servers and all of these connect to each other using sockets over a private lan! And the standalone mysql server is firewalled harder than 'The Great Firewall of China'!!?? Then what do you do? Ask the question anyway?

    "No!" I say. Read the code, else if, search the forum, else if, refer back to the documentation. If all else fails, then submit a query. So that's what I did.

    Turns out the venerable Carl Hancock answered the question in another post. (and I used pencil and paper to make notes in my $2, college ruled notebook labeled 'Server'). The note reads:
    "Entry data goes into rg_lead, re_lead_detail & rg_lead_detail_long tables. They are stored across multiple tables to for max performance"

    Long story short (lol), it just works. I exported the 3 tables to a single .sql file. Then exported the .sql file to the new server. If you're on a single site, you're done. If you're on multisite change the #(id) of your table to match the #(id) of the site in the receiving (new) db. **Remember to set your form up before messing around with the db**

    My one advice is; don't use phpMyAdmin. You'll avoid a wide variety of headaches, present-past-and-future by using open source apps made for maintaining mysql databases. Look at http://www.mysql.com/downloads/workbench/ It is OS agnostic. It may not come easy, it may take some time, but get it configured and working. Use google to find alternatives for your OS. I use OS X, and sometimes use Sequel Pro (free) for quick stuff.

    Ciao! Thank you! And have fun taking your entries wherever you may roam!

    *edit - changed 2nd paragraph to an ordered list for presentation

    Posted 13 years ago on Tuesday September 20, 2011 | Permalink
  2. How nice to see this as my last unread post of the evening. Thanks for posting your experience. I'll make sure the rest of the team sees this.

    Posted 13 years ago on Tuesday September 20, 2011 | Permalink
  3. I can confirm that this works. In my case, I needed to export rg_lead, re_lead_detail, rg_lead_detail_long, rg_lead_meta, and rg_lead_notes. Make sure you make backups though—it took me several tries to get it just right using Sequel Pro.

    Posted 13 years ago on Saturday December 10, 2011 | Permalink
  4. Thank you mtbethel for posting your experience.

    Posted 13 years ago on Saturday December 10, 2011 | Permalink