The Community forums are being phased out in favor of a new Slack group.
Add your email address below to get an invitation to join the community slack group

Slack Signup
Newsletter Optin
Help Desk

Migrating data and forms to new site

Labels

This Discussion is public

Notifications

I need to move my forms, views and data to a new site and am looking for some advice. I want to be sure we don’t lose anything.

Hi,

You can always use the export / import feature, however I have never done this for all my forms, views, and data.  I have several of each on a single site ...

Another approach that works for me is migrating your the whole wp site, including all of the formidable stuff to the location of the new site, and converting the target copy of the current site to the new site.

That works fine for me as my current and new sites do not differ significantly and I get an exact copy of all the formidable stuff (nothing missing).

So, this may or may not be an option for you.

Just a suggestion, hope it helps ...

Kevin

Marty,

You can export everything via Formidable's export process as XML files and then import to the new site.

One thing to watch with this process is that your forms/views may import as different shortcode numbers.  I've experienced this with exporting forms from one site to another and the views or searches no longer worked, since they were looking for different field or form shortcode numbers.

If possible I would do as webnextlevel had mentioned and migrate the entire site.

Good luck.

If you built your views and form emails using field ids instead of field keys, these will all need to be edited when imported to the new site. Fields ids change on import. Field keys remain the same. Views and form emails are not updated to reflect id changes. I learned a long time ago to reference fields by their keys as a standard practice rather than their ids.

Hi vfontjr, thanks for the best practice tip!

I typically use whole site migrations for major data migrations involving formdiable.  But I will try some export/import data migrations using keys instead of ids at some point to see if its an option for me.

I have very many references to view, form, and field id's thoughout my app.  Wish there was a way to one-click wau to switch from ids to keys.  :)  Going though and changing them though would like be a good exercise to help with documenting my app.

Cheers

Discussion closed.