Move a form between accounts with export and import
Export and Import Form on the Forms list move a form's settings between accounts. Duplicate makes a copy inside the same account and is described on the same page.
Before you start
- Import needs the account to have an AroFlo credential. On the Free plan it is only offered while the account has no forms, and an imported form counts as the account's one form.
- A file made from a Simpro or Fergus booking form is refused. The message names the product the file came from and says to import it on that product's booking forms page.
Step by step
To export:
- Open the Manage menu on the form's row in Forms and click Export.
- Wait for the steps to finish. The file downloads, and the popup lists what it kept and what it left out.
To import:
- Click Import Form and drop the
.jsonfile in. Files are held to 2 MB, and the form inside must be under about 900 KB. - Under Review, check the Form name. It must be 3 to 100 characters. If a form already has that name, the page offers a new one.
- Read Needs attention, Left out and Kept, then click Import.
- Click Open form. The form is new, with new ids for its services, time groups and categories.
What does not travel
A form is exported as everything it holds, less what belongs to the AroFlo account it was made in. These are left out, on export and again on import:
- The AroFlo business unit, task type and priority. The form can't be saved or used until you choose your own on Form Properties and Booking Task Type.
- Custom field mappings. Map them again on Custom Fields.
- Payment settings, which hold the Stripe or Square connection. Set them again on Payments.
- AroFlo users: staff rows, the default calendar's staff, team members, callback users and region rosters. Choose staff again on Service Calendars.
- Regions, which are drawn once on the account.
- Notification recipients, so the old business is not emailed about the new account's bookings.
- Conditional intros, which name clients and sites in the first AroFlo account.
- The captcha connection and anything else that is a key, a secret, a tracking id, an integration, a webhook or a user id.
- Internal notes, and the address of the page the auth links point to.
- Embed state. The imported form is not on any page until its embed code is added to one.
Event names for Google Analytics, Tag Manager and the Meta pixel are kept. The Geosearch home address is kept and flagged, since it is the exporting business's address.
A redirect address that is not a web address is dropped, so customers see the thank you message. Text and style settings are cleaned of scripts, event handlers and links that run code, and the summary says how many were taken out.
What import switches off
Geosearch, Dynamic travel times (billed per route) and Travel blocks on the calendar are turned off on import whatever the file says, so nothing is billed until you choose. Turn them on again on the Geosearch page.
On the Free plan the Business settings in the file are saved but not used. The summary lists them under Free plan, and they apply once the account is on Business.
What to check after an import
Needs attention lists the settings that came across and need a look: the Time zone (it must be the time zone of the business taking the bookings, or every time offered will be wrong), a Redirect address customers will be sent to, the Geosearch home location, and Staff to pick for any service with nobody to take it. Each item with a page has an Open button.
When it goes wrong
"A form named {name} already exists."
Choose another Form name under Review.
"The file is incomplete and can't be imported." or "The form in the file is too large to import."
The file was cut short, edited by hand, or is bigger than a form can be once saved. Export it again.
"This file is an export of a Fergus booking form. Import it on the Fergus booking forms page, not here."
The file is from another booking product. The same message names Simpro for a Simpro file.
The imported form says Setup needed
Expected. The business unit, task type and staff were left out. See Use the setup checklist.
"Settings in the file are not recognised by this version"
The file came from a newer build of Formpiece. Those settings are kept as they are and may not work.