Moving from one form plugin to another means migrating form structures, existing entries, and any integrations connected to those forms — none of which transfers automatically between different plugins, since each stores this data in its own specific way.
Form migration between plugins
Forms, entries, and integrations migrated to a new plugin, tested on staging before going live.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Confirmation of your current and destination form plugins
- Confirmation of which forms and how much historical entry data needs migrating
- A staging environment, or agreement to have one created, for testing the migration safely
This or something else?
| You want to migrate forms, their entries, and integrations from one plugin to another | This fix covers it |
| You want to export entries and recover data, not migrate to a new plugin | Form entry export & data recovery, a different kind of task |
| You’re not changing plugins, just fixing an issue with your current one | The relevant specific fix for your actual issue instead |
| You want form accessibility issues fixed as part of this migration | Worth flagging — we can address known accessibility concerns during the rebuild if you specify |
What we do
- Map your current forms’ structure, fields, and logic to the destination plugin
- Test the migration on a staging copy before touching the live site
- Migrate form structures, then historical entries where feasible
- Reconnect any integrations (email routing, CRM, payment) to the new plugin
- Verify the migrated forms function identically to the originals
- Confirm the live site’s forms work correctly before considering the migration complete
What is included
- Forms migrated to the destination plugin with structure and logic preserved
- Historical entry data migrated where technically feasible
- Integrations reconnected and tested
- Staging environment testing before any live change
Not included
- Recovering entry data that isn’t feasible to migrate given format incompatibility between plugins
- Redesigning forms beyond what’s needed to replicate existing functionality
- Choosing which form plugin to migrate to — that’s your decision, though we can share technical observations if asked
- Ongoing support for either the old or new plugin beyond this migration
Questions about this fix
Will all my historical entries transfer to the new plugin?
We migrate what's technically feasible given how each plugin stores its data, though very old entries or complex field types don't always map cleanly between different plugins — we'd flag any limitation specific to your situation before starting.
What happens to my integrations, like a connected CRM or payment processor?
We reconnect these to work with the new plugin, since integrations are typically tied to the specific form plugin's own connection method rather than transferring automatically.
Why do I need to test on staging first instead of just doing it live?
A form migration touches structure, data, and integrations together, and testing on staging first means any issue is caught and resolved before it affects your actual, live forms and the visitors submitting them.
Will my forms look and behave exactly the same after migration?
We aim to replicate existing structure and logic as closely as the destination plugin allows — some visual differences are possible depending on how differently the two plugins render forms, which we'd flag if relevant.
How long does a typical form migration take?
It varies with the number and complexity of forms and how much historical data needs migrating — we'd give you a realistic estimate once we understand your specific scope.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.