Kindly EditDocumentationTry the editor

Templates and importing forms

Start from one of 28 templates, move forms between sites, and import Fluent Forms and Gravity Forms forms and entries with notes on what to check.

A new form can start blank, from one of 28 finished templates, or from a file: a Kindly Forms export from any site, a Fluent Forms export or a Gravity Forms export. On a site that still has Gravity Forms, its forms can be brought over directly, with their add-on feeds and, if you like, their entries. This page lists the templates and explains what an import brings over and what it reports for you to check.

All three start in the same place: Kindly Edit > Forms, New form. The window asks what to Start with: Blank (name, email and message, ready to change), From a template, or Import a file, plus From Gravity Forms when Gravity Forms' forms are on this site. Make the form creates it and opens the builder.

Templates#

Choose From a template, then pick one. Search templates looks in names and descriptions, and Category narrows the list. Choosing a template fills in the Name if it is empty. The new form is an ordinary form: change anything.

Every template comes with its fields, a thank-you message and its emails. Most send an Email to the office (to the site's admin address, with every answer and the page it came from) and some also send an Email to the sender. Check the recipients before you publish.

Template Category What it asks
Contact Contact and requests Name, email, phone, subject and message, with a copy to the sender.
Quote request Contact and requests Service, budget, timing and project details, with an optional attachment.
Support request Contact and requests Topic, priority, page and description, with screenshots. Urgent requests get their own email.
Appointment request Contact and requests Service, preferred day and time, and how to reach them.
Newsletter signup Contact and requests Email, first name and topics, with double opt-in so only confirmed addresses count.
Request a callback Contact and requests Name, phone, best time to call and what it's about.
Real estate inquiry Contact and requests Buying, selling or renting, property type, budget, bedrooms, area and timing.
Bug report Contact and requests Page, severity, browser and device, steps to reproduce, expected and actual results, screenshots.
Event registration Events Attendee details, ticket type, guests with their meals, and dietary needs.
RSVP Events Will they come, how many, and their meal. Meal and guests show only for a yes.
Conference proposal Events Speaker details, session title, format, track, abstract, bio and slides.
Job application Registrations and applications Three steps: about you, experience with a resume upload, and final questions.
Volunteer signup Registrations and applications Interests, available days, how often and experience.
Membership application Registrations and applications Three steps: about you, membership level and interests, then agreement and signature. Entries wait for approval.
School admission Registrations and applications Three steps: the student, the parent or guardian, and documents.
Donation Payments Preset gift amounts or their own, a dedication and the payment method.
Order form Payments Products with quantities, shipping address, coupon, order summary and payment.
Customer satisfaction survey Surveys and feedback Overall rating, Net Promoter Score, a rating grid and comments.
Course feedback Surveys and feedback Course and instructor ratings, agreement scales and suggestions.
Feedback with follow-up questions Surveys and feedback A rating; low ratings ask what went wrong, high ratings ask what went right. Low ratings get their own email.
Testimonial Surveys and feedback Rating, testimonial, photo and permission to publish. New ones wait for approval.
Quiz Quizzes and polls Scored questions with right answers and letter grades shown at the end.
Personality quiz Quizzes and polls Each answer leans toward a type; the most chosen type is the result.
Poll Quizzes and polls One question; after voting, people see the results so far.
Petition Signatures and agreements The petition text, signer details, a comment and a drawn signature. The count shows after signing.
Waiver and release Signatures and agreements Participant and emergency contact, the waiver to read and accept, and a signature.
User registration Accounts and posts Makes a WordPress account with the name, username and password people choose.
Post submission Accounts and posts Visitors send a post with title, content, category and featured image; it waits as pending for review.

Donation and Order form need the payment fields. A site without them doesn't list these two. Set up a payment method before publishing them: see Payments.

Developers can add folders of their own templates with the kindly_forms_templates_dirs filter, and change the list or a template's definition with kindly_forms_templates and kindly_forms_template. See the developer reference.

Move forms between sites#

Export a form from its menu in the forms list, or tick several forms and choose Export. You get one JSON file: named after the form for one, or kindly-forms- and the date for several. The file holds each form's latest saved version (unpublished changes included), with its fields, settings, emails and connections.

On the other site, choose New form, Import a file and pick the file under Forms file (.json). Each form in the file becomes a new form there. A form that was closed (draft) stays closed. Forms are never merged into existing ones.

What the file does not carry:

  • Entries. Export them separately from Entries, and import them into the new form (see below).
  • Site-wide connection keys and accounts. Connect the services again on the new site under Connections.
  • Pictures and files are referred to by their Media Library IDs, which differ between sites. Choose them again.

A file larger than 20 MB is refused.

Import from Fluent Forms#

In Fluent Forms, open Tools, then Export Forms, choose the forms and download the JSON file. In Kindly Forms, choose New form, Import a file, and pick that file. The help under the file box reads Kindly Forms, Fluent Forms or Gravity Forms exports.

Each form in the file becomes a new Kindly form. A form that was published in Fluent Forms is open here; any other status comes in closed. When everything carried over exactly, the builder opens (one form) or the forms list shows them (several). Otherwise a summary lists each form with what to check, and any forms that were skipped with the reason.

The file is read as data only: nothing in it runs. Every value then goes through the same cleaning as a form saved in the builder.

What comes over#

  • Fields, with their labels, names, help text, placeholders, defaults, required setting, unique-answer checks, prefixes and suffixes, label position, width class and conditions.
  • Layout: columns (up to six in a row), steps with their titles, progress style, animation, saving progress per step and moving on automatically, collapsible sections, repeating groups and repeating rows.
  • Validation: lengths, number ranges and digits, input masks, choice limits, date limits and file types and sizes.
  • Choices, including "Other", choice layouts, picture choices, calculation values, dynamic choices from posts, terms or users, and linked drop-downs.
  • Calculations, with Fluent's formulas rewritten in Kindly's form.
  • Smartcodes such as {inputs.email} and {all_data}, in labels, messages, emails and connections.
  • Confirmations: the default and the conditional ones, as a message, a page or an address.
  • Emails: recipients (an address, an answer, or routing by conditions), subject, body, from, reply-to, copies, attachments from upload fields and the Media Library, conditions, and whether they go on sending or after payment.
  • Restrictions: entry limits, schedule, signed-in only, refusing empty sends, and IP, country and keyword rules.
  • Double opt-in, admin approval and the answers page.
  • Survey results after sending, privacy (not keeping entries, deleting after some days) and the setting that offers the form to AI assistants.
  • Save and finish later, with its message and email.
  • Conversational look and landing page, with their colors and words.
  • Quizzes: right answers, points, grades and personality results.
  • Captchas: one per form.
  • Post fields become a "Create a post" connection with the same mapping.
  • Connections for every service Kindly has a provider for. Webhook, Zapier, Slack, post creation, user registration, user update and Mailchimp come over with their mapping; the others are matched by field name and listed for a check.
  • Payment fields, when payments are on this site: products, subscriptions, custom amounts, quantities, payment methods, the order summary and coupons. Only the currency comes from Fluent's payment settings.

Shortcode and server hook fields, and the form's custom CSS, come over only for people who may add code to the site (the unfiltered_html capability), as in the builder.

What produces a note#

The summary says, form by form, what didn't carry over exactly. The same notes are kept with the form. They cover:

Kind Notes you may see
Fields A field type with no Kindly match was left out (named, with its Fluent type). A number of fields couldn't be kept. A field's own messages for some checks now use the form's messages. Option groups became one list. Advanced date setup written as code wasn't brought over. Executable files (exe) are never accepted. A masked column in repeating rows became plain text. A CSV for linked drop-downs wasn't in the export. Extra post queries weren't brought over. Dynamic choices need their filters checked.
Masks A mask has letters that Kindly reads as typing slots. A mask had optional or repeating digits; in Kindly every slot is needed.
Layout Columns inside columns were laid out one after another. A row had more than six columns. A page break inside a container was left out. Step tabs are shown as step names. Picture buttons became word buttons. The send button's own colors weren't brought over.
Look The form's extra CSS class wasn't brought over. Custom CSS came over but its Fluent selectors don't match Kindly's markup, or it was left out without the code permission. Custom JavaScript wasn't brought over. Styler colors and spacing weren't brought over. The conversational background picture isn't in the Media Library, and conversational button words use Kindly's wording. The landing page's own HTML wasn't brought over.
Smartcodes and logic Smartcodes with no Kindly match were left as written (listed). Conditional text ([ff_if] shortcodes) was kept as written and isn't read. A calculation uses Sigma() or Pi(), or nCr or nPr (use comb(n, r) or perm(n, r)). Advanced validation has no Kindly match.
Emails and confirmations A confirmation page isn't on this site. Some Media Library attachments aren't on this site. PDF attachments and PDF feeds weren't brought over (set them up in the Documents tab). Emails sent as raw HTML now use Kindly's email layout.
Connections A connection has no Kindly provider and was left out. A connection's field mapping was brought over by name. Mailchimp tags chosen by conditions became tags added when an answer is given.
Payments A payment field was left out because payments aren't set up. A payment field came over; check its prices. A product had its own quantity box (add a Quantity field). Stock needs setting again. Payment methods without a Kindly gateway were left out. Only the currency came over from payment settings. AffiliateWP referral settings weren't brought over.
Quizzes A question scored when an answer is left out. Points per choice became calculation values. Grades set in points became percents.
Captchas and code Only one captcha is kept per form. Shortcode and server hook fields were left out without the code permission.

A form that can't be read at all is skipped, with the reason: It isn't a form. or Its fields couldn't be read.

Import from Gravity Forms#

Gravity Forms import is in Kindly Edit 0.12.0 and later. There are two ways in:

  • From Gravity Forms (on the site where Gravity Forms is installed): choose New form, From Gravity Forms, tick the forms (active forms not yet imported start ticked) and choose Make the form. This reads Gravity Forms' own tables, so the add-on feeds come over too: Authorize.Net, ActiveCampaign, iContact, Mailchimp, Coupons, Partial Entries, webhooks and analytics event tracking. Bring their entries (off at the start) also copies each form's entries, with their dates, read state, network address, page and payment summary. Spam and trashed entries stay behind.
  • Import a file: in Gravity Forms, open Forms, Import/Export, Export Forms, and pick that file in Kindly Forms. Gravity's file has no add-on feeds, so connections and payments come over only through From Gravity Forms (a file whose forms carry a feeds list, in the shape of Gravity's feed table, is read too).

Show for [gravityform] shortcodes and blocks (on at the start) keeps the Gravity form's number with the Kindly form, so pages that use [gravityform id="12"], [gravityforms id="12"] or the Gravity Forms block show the new Kindly form. While Gravity Forms is still active, only imported forms are taken over; every other form is still drawn by Gravity Forms. Once Gravity Forms is switched off, a number nobody imported shows nothing. Each imported form has a Gravity Forms section in its Settings to turn this off. Importing the same Gravity form again makes a new Kindly form, which then stands in for it.

Keys are never brought over. A feed's own API keys, add-on settings and webhook secrets stay behind. The summary starts with Keys to enter and names the connections and payment services that need their keys in Connections and Payments.

What comes over from Gravity Forms#

  • Fields: text, paragraph, drop-down, multi-select, number, checkboxes, radio buttons, hidden, name, email (with its confirm box), phone, address, website, date, time (as a checked text box), file upload, list (as repeating rows), consent, HTML, section, page, signature, image and multiple choice, and post fields. Labels, descriptions, placeholders, defaults (dynamic population becomes {get.param}), required with its message, no duplicates, CSS classes, label placement and hidden or staff-only visibility.
    • Field keys are made from the labels. A long one is cut to 48 characters and stays the same when the form is saved again.
    • A drop-down without a placeholder starts on its first choice, as in Gravity Forms. This includes product drop-downs, and drop-downs filled from the web address when the address has nothing for them.
    • An address's country starts on Gravity's default country, usually none.
    • A consent field's label shows as a label line above the agreement.
  • Layout: fields Gravity puts in one row become columns, pages become steps named after Gravity's page names with their button words, and Gravity Fieldset groups (Fieldset Begin and End) become a box. A section with conditions hides every field after it up to the next section or page break: each of those fields gets the section's conditions along with its own.
  • Payments: products (one price, choices, drop-down, typed price, hidden and calculated), options, quantities (a product's own quantity box becomes a Quantity field), shipping, coupons, total and the card field (as a Payment method taking Authorize.Net). GP eCommerce Fields tax and discount fields become Tax and Discount fields, and GP Conditional Pricing becomes the products' Price when rules (a rule on a product's quantity reads that product's quantity). A product's own quantity box and Gravity's Quantity field start empty, as in Gravity: the product counts once a quantity is typed. An Authorize.Net subscription feed turns the product it bills into a subscription plan with the feed's interval, number of payments and setup fee. When it bills an amount the visitor types, the subscription gets Visitors choose the amount, with a Smallest amount of 0.01 when Gravity required the amount. A Coupons feed makes a Kindly coupon (Payments, Coupons) unless that code already exists. When the Authorize.Net feed only ran under conditions and the card field has its own conditions (for example, a choice to pay by check), the card field keeps them: when it is hidden, the entry keeps its total as unpaid. The form's notes ask you to check that the card field's conditions match the feed's. A form with products but no payment feed charged nothing in Gravity, so its Payment method field comes over switched off by a condition that never holds: each entry keeps its total as unpaid. Remove that condition to take payments.
  • Conditions on fields, pages, confirmations, emails and feeds, including GP Conditional Logic Dates rules on today's date and the time now. See Dates and the time now. A rule on a field the Gravity form no longer has reads it as empty, as Gravity does. A rule on a field Kindly can't import is left out.
  • Calculations, with merge tags rewritten and Gravity's rounding kept.
  • Merge tags such as {Name:1.3}, {all_fields}, {pricing_fields}, {user:display_name} and {embed_url} become Kindly smartcodes in labels, messages, emails, confirmations and feeds. {Total} becomes the payment total. HTML field words and the form description change only where a tag has a Kindly match. Tags Kindly can't fill print what Gravity printed:
    • A tag for a field the form doesn't have stays as written.
    • A part of a field with one answer prints the whole answer.
    • A part that a field with parts doesn't have prints nothing, so the tag is removed.
  • Confirmations: messages, pages and redirects with their query and conditions. Gravity's save-and-continue messages aren't confirmations; Kindly shows its own when answers are saved for later. A page confirmation whose page content has merge tags gets Fill smartcodes on that page (GP Post Content Merge Tags).
  • Notifications: to an address, to an answer or by routing rules, with from, reply-to, copies, conditions, file attachments, and whether they go on sending or after payment.
  • Settings: label placement, send button words, entry limits, schedule, signed-in only, save and continue, IP address privacy and entry retention, honeypot, and Akismet when Gravity's site-wide Akismet setting is on. With From Gravity Forms, when Simple Cloudflare Turnstile is active and guards Gravity forms, each form it guarded gets a Turnstile Captcha field.
  • Survey fields: likert (a choice grid, or one row as Choose one), rank, rating and the plain kinds.
  • GP Copy Cat classes (copy-1-to-2) on a checkbox and Gravity's "same as" address option become When ticked, copy. GP Inventory limits become stock on the choices.
  • Feeds: ActiveCampaign (list, fields, tags, note, responders; custom fields by their ActiveCampaign field id), iContact, Mailchimp (switched off if it was), webhooks (secret headers emptied), Partial Entries (Save partial answers) and analytics event tracking (events on). With From Gravity Forms, a feed whose Gravity add-on is switched off on the site (so it never ran) comes over switched off.

Gravity Forms notes#

As with Fluent Forms, the summary lists, form by form, what didn't come over exactly, and the notes are kept with each form. They cover: field types with no Kindly match (such as chained selects), fields only staff saw, a condition on a field that isn't in the form (read as empty) or that has no Kindly match (left out), date boxes or drop-downs that became one date box, survey scores, quiz answers, poll results, picture buttons, a Next button's own conditions, the form's CSS class, emails sent when answers are saved for later or through another mail service, feeds with no Kindly connection (such as Zapier), a CiviCRM feed ("CiviCRM connection not imported"), a feed imported switched off because its add-on was off, ActiveCampaign custom fields that Gravity would have created by name and Mailchimp groups to choose again, save-and-continue messages that weren't brought over, a Turnstile captcha that needs its keys in Forms settings, Spam, an Authorize.Net feed with its own keys or its own conditions, a paid trial that became a free trial, a form with products that charged nothing because it had no payment feed (its payment field is off), a subscription that billed a calculated amount (which can't be a plan), option prices that aren't multiplied by the product's quantity, merge tags with no Kindly match (left as written), and merge tags for a part their field doesn't have (removed).

Import entries#

Entries come separately. In Entries, choose the form, then Import. The file can be a CSV with a header row, such as an entries export from Fluent Forms or a spreadsheet, or a JSON entries export from Kindly Forms.

  1. Pick the File and, for a CSV, how Columns separated by (or Work it out).
  2. Continue reads the file. For a CSV, match each column to a field under Goes into, or Skip this column. The first value of each column is shown beside it.
  3. Import adds the entries. Empty rows are skipped and counted.

People who may delete entries can tick Delete this form's current entries first. It asks once more before deleting: this can't be undone. An import takes up to 20,000 rows (filter kindly_forms_import_max).

About this page

Documents Kindly Edit 0.9.16. Source: includes/forms/templates.php, includes/forms/data/templates/, includes/forms/import.php, includes/forms/import-gravity.php, includes/forms/gravity.php, includes/forms/admin-data.php, assets/forms/admin.js. Theme choices and account permissions can change which controls appear.

Type a word or phrase to search the full documentation.