What This Article Covers

Solution Launchpad is available through the Keap certified partner program. A custom field is an optional field you create to extend a contact or company record beyond the default fields. For example, you could create a custom drop-down field to store a contact's preferred service type or a text field to store their account number. This article covers what is included when a custom contact or company field is installed from one app to another using Solution Launchpad, and the rules that govern how duplicate fields and field limits are handled during installation.

To learn how to become a certified partner and access Solution Launchpad, see how to become a Keap Certified Partner.

What Is Included When Installing a Custom Field

When a custom contact or company field is installed from one app to another using Solution Launchpad, the following data is transferred to the destination app:

• Field label — the name displayed on the contact or company record
• API field name — the unique identifier used by the Keap API to reference the field
• Field type — such as text, drop-down, date, or checkbox
• The Always shown checkbox setting — whether the field is always visible on the record even when empty

All field types are supported during installation, provided the destination app's edition supports the same field type.

How Custom Field Installation Behaves

The following behaviors apply when a custom field is installed into a destination app using Solution Launchpad:

• Duplicate fields are skipped. If the destination app already contains a custom field with the same field type and API field name, Solution Launchpad will not install the field again. The existing field in the destination app is left unchanged, even if the field configuration in the source app has been updated since the original installation.
• Existing items are updated to reference the matching field. If other items being installed in the same bundle reference the custom field, and a matching field already exists in the destination app, those items will be updated automatically to reference the existing field rather than creating a duplicate.
• Installations that exceed the custom field limit will fail. Each app edition has a maximum number of custom fields allowed. If installing a custom field would push the destination app beyond its custom field limit, the installation will fail. See custom field limits and how to manage your custom fields for information on the limit that applies to your edition.