Migrating from the legacy (and sometimes buggy) 1.0 WordPress e-Signature plugin is easy – 90% is just copy and paste including the shortcodes.
To migrate your WordPress e-Signature Plugin to SwiftCloud-Docs, we recommend the following steps:
- Pick any plan on https://swiftcloud.ai/products/electronic-signature and get signed up. All plans have a 60 day money-back guarantee and this can be setup in just minutes, so do that first.
- Once in, create a new doc i.e. whatever you want signed – just a page title for you.
- Find the little blue button with a white pen, and select “Quick Start Setup”, then delete everything in the main page body area (you’re going to replace it).
- Next, get logged into your WordPress admin and get to the backend of your e-signable page. Copy the entire page, shortcodes and all.
- Paste that into the new doc you created (the newly blank SwiftCloud doc).
- Delete the following:
- The very first line i.e. [swiftsign swift_form_id=”1234″ fullpagemode=on]
- The very last 2 lines – [swift_button] and [/swiftsign]
- Next, click Save at the bottom and then click Preview to see your doc.
V1 Users: Old docs will continue to be accessible for several years to come, but new signatures will be blocked Sept 2018.
You’re more or less done!
Also ensure the section right below the main-doc, the “User Experience Flow” has some action – usually you want to send them back to your WordPress site to a thanks page, but you could send them right to payment, etc.
Most shortcodes have purposely stayed the same. Note .AI is 2.0, and .IO is 1.0 – these look similar on purpose but we have started to retire and migrate all clients. The WordPress Plugin will stay active, but will switch to handling just receipts, tracking, hidden marketing variables, and other related non-signature functions.
A Note on Signed Docs in 1.0…
NOTE: This only applies to users of our “alpha system”, which was a WordPress Plugin.
If you have docs that have been signed using the 1.0 system, we recommend the following:
- Migrate your signable doc(s) per above, so that any new signatures happen on the 2.0 platform (.AI, not .IO)
- Once done, re-link your site’s e-sign intake to your signable docs on SwiftCloud.AI (not IO), instead of your e-Signable WordPress pages.
- IF you have all the old signed docs downloaded, then you can delete the plugin and pages, but if you have not downloaded them all, you may wish to leave the plugin installed but set it to inactive and unpublish (back to “Draft”) or password protect the e-signable pages. In case you need to dig out a previously-signed PDF you’ll need access to the WordPress page and signature-data (on the old IO platform, which will continue to be accessible but won’t accept new signatures).
What could we do to improve this?