Move forms and resources between GlobalForms servers, for example from a test server to production, or keep them as backups.
Export
-
One form or resource: select Export next to it on the designer home page. Any resources it uses are included.
-
Everything: select Export All in the title bar.
A .json file is downloaded. Exports contain form designs, actions and settings, not submissions.
Import
-
Select Import in the title bar.
-
Choose one or more exported files and select Import.
-
GlobalForms checks each form and resource in the file against your server and shows what it will do. For each item that already exists, choose an action:
|
Action |
Result |
|---|---|
|
Skip Update |
Leaves the existing item unchanged |
|
Overwrite |
Replaces the existing item with the imported one. Use this to move a tested form to production. |
|
Merge |
Combines the existing and imported versions as best it can. Always test a merged form thoroughly. |
|
Create Copy |
Imports the item as a new copy named "Copy Of …" |
Complete the import, then refresh the page to see the imported items.
Protected forms
Some forms are never changed by an import, such as the user login form and hidden system forms, even if the file contains them. You can protect more forms. See Import Protection.
Things to consider
-
Import forms into the same or a newer GlobalForms version than the one they were exported from.
-
Server settings in
local.json, such as SQL connections, Resquel routes and email, are not part of an export. Set them up on the destination server too. -
Forms that use passwords stored in actions, such as older PDF Snapshot actions, carry those passwords in the export file. Use server-stored credentials instead. See PDF Snapshot Action.