You can copy a single or multiple custom fields from an account to another. Distributing custom fields makes it easier to keep the systems, connected accounts in sync.
For more information on custom field distribution, watch the November 2024 Product Release video:
Additional distributable assets
To learn more about the assets you can distribute to other accounts, see the following pages:
Distributing a custom field
Before distributing a custom field, please see section Essential information when distributing custom fields.
- Go to the Management > Field Editor page.
- Click the Distribute a copy to another account icon next to the field you would like to distribute.
Please note that system fields cannot be distributed.
- Select the Target Account where you would like to distribute the fields.
- When the field is distributed, you will receive a notification both in the source and target accounts.
Distributing multiple custom fields
Before distributing multiple custom fields, please see section Essential information when distributing custom fields.
- Go to the Management > Field Editor page.
- Select the fields you would like to distribute to another account and click the Distribute Selected button.
Important:
- Please note that system fields cannot be distributed. If you have also selected system fields, then those will not be distributed.
- You can distribute a maximum of 100 custom fields at the same time. The field type of the selected fields does not affect this limit.
- Select the target account, where you would like to distribute the fields.
- To check if there are any issues with the selected fields, click the Review Errors button.
- When you are ready, click Launch Distribution.
After launching the distribution, the Bulk Field Distribution Is in Progress notification is displayed and you can navigate away while the process is completed.
- When the fields are distributed, you will receive a notification both in the source and target accounts. To check the results, click Distribution Report.
Essential information when distributing custom fields
Four properties are relevant when distributing custom fields:
- Field ID
- String ID
- Field Name
- Field Type
Field matching between the source and target accounts is based on the Field Name (in English) and Field Type properties.
Since fields are matched by their English names, English should not be restricted on either the source or target account. Additionally, at least one common language must be enabled on both accounts to initiate the distribution process.
Values are handled during custom field distribution as follows:
- Custom field values: Values or choices for single- and multi-choice fields will be distributed.
- Contact field values: The actual field values of your contacts will not be copied. The newly distributed field will have empty values for the contacts.
During distribution, if no matching field (having the same name and type) exists on the target account, a new field will be created with all the original details (Field Name, Field Type, String ID, choices, translations, etc.), however, it may have a different Field ID.
An example:
| Source account | Target account | ||||
|---|---|---|---|---|---|
| Field ID | String ID | Field Name | Field ID | String ID | Field Name |
| 11 | last_purchase | Last purchase | 12 | last_purchase | Last purchase |
Additional cases blocking custom field distribution
- The field exists on the target account (the Field Name and Field Type properties match, but it has a different String ID): If a field with the same name and field type exists on the target account but has a different String ID, it is treated as the same field during distribution. The String ID mismatch is ignored in this case.
An example:
| Source account | Target account | ||||
|---|---|---|---|---|---|
| Before distribution | |||||
| Field ID | String ID | Field Name | Field ID | String ID | Field Name |
| 11 | last_purchase | Last purchase | 12 | last_purchase_2 | Last purchase |
| After distribution | |||||
| 11 |
last_purchase |
Last purchase | 12 |
last_purchase_2 |
Last purchase |
- The field does not exist on the target account (but a field exists with the same String ID): If the source field does not exist on the target account, but a field with the same String ID does, an error message will be shown in the distribution dialog indicating a mismatch blocking the distribution. We recommend updating the String ID on either the source or target account.
| Source account | Target account | ||||
|---|---|---|---|---|---|
| Field ID | String ID | Field Name | Field ID | String ID | Field Name |
| 11 | last_purchase | Last year purchase | 12 | last_purchase | Last purchase |
- The field does not exist on the target account (but a field has the same String ID as one of the source field's translations): If the source field does not exist on the target account, but a field on the target account shares the same String ID as one of the source field's translations, an error message will appear in the distribution dialog. We suggest updating the String ID on either the source or target account.
| Source account | Target account | ||||
|---|---|---|---|---|---|
| Field ID | String ID | Field Name | Field ID | String ID | Field Name |
| 11 | last_purchase_fr | Last year purchase | 12 | last_purchase_fr | Last purchase |
Known issues and limitations
- System fields cannot be distributed.
- You can distribute a maximum of 100 custom fields at the same time.
- Field IDs are not copied to the target account when distributing custom fields.
- Currently, field names are only available in English without translation.