In Pipeliner, data can be pre-filled from one entity to another when creating a new record that is related - for example, when adding a new Contact to an Account record, the address pre-fills from the Account to the new Contact using system mappings.

It is also possible to create custom "conversions" from one record type to another. For example, it may be that in your environment, you want users to convert data being captured within Leads to Accounts as well as Qualifying good Leads to become Opportunities.

The Field Mapping Add-on enables Admins to:

NOTE: Field Mappings is a chargeable add-on for all Tiers except Unlimited

Once enabled in the Automation Hub in the Admin Module, the Field Mapping Add-on will be available as a new sub-tab for all entities in Admin, except Product and Product Line Items. All system hardcoded relation mappings will be available for the Admin to change and new mappings can be created for custom entities. New relation mappings and new conversion mappings can be created by clicking on "Create New" ⤵

and existing mappings amended and updated by selecting and then clicking on "Edit Mapping" ⤵

System mappings cannot be deleted but can be modified or, subsequently, reset back to the system default behaviour. Select an existing relation and then click on "Edit Mapping" ⤵

System field mappings are noted on the form and can be reset to the default behaviour by unticking the checkbox to disable the custom mapping ⤵

To add a new or to change an existing field mapping, enable the checkbox and then select the field from the original record that should be mapped to this field on the new record ⤵

Field Mappings for custom relations are created from scratch by clicking Create New>New Relation Mapping ⤵

Choose the entity you want to work with ⤵

and then select the field(s) to be mapped ⤵

If the field is a validated field - dropdown, multi select checkbox or radio - click on Set Field Mapping to map how each value should map ⤵

Click on "Create New>New Conversion Mapping" ⤵

and select the entity you want to convert to and then click "Save". Your conversion mapping will be created, select it and click on "Edit Mapping" to set up which field data should transfer to the new record ⤵

Set up your field mappings by enabling the checkbox for each field and then choosing which field from your originating record should map to the field on the record created by the conversion ⤵

When you've finished mapping all your fields, click "Save".

For Relation Mappings, in User Settings, the setting “Auto-populate data when creating a new Account or Contact” has been changed to “Auto-populate data when creating a new related record”. When enabled, this switch will now affect all prefills ⤵

During creation of a new record, there will be no change to the user experience. Prefills will be applied based on the system or custom mappings from the existing record to the new related record. If at least one field was prefilled, there will be a yellow banner at the top with Undo/Populate button and any prefilled field will be also marked in yellow ⤵

For new Conversion Mappings, users will see a "Convert" button on the main record toolbar ⤵

You'll need to choose what should happen to the originating record ⤵

The new record will then be previewed and you need to click on "Convert" to create it ⤵

NOTE: Field Mappings is a chargeable Add-on for all Tiers except Unlimited

When you use a Relation Mapping, you are creating a new record that is linked to the originating record - for example, if you're on an Account and you create an Opportunity using a Relation Mapping, the new Opportunity will be related to the originating Account and data from your mapped fields will have pre-populated fields on your new Opportunity.

In contrast, a Conversion Mapping will create a new record pre-populated with your mapped fields from the originating record but there will be no relationship, or link, between the 2 records - in fact, depending on the option you select when converting, the originating record may even be deleted (or archived). You might use this option when a Lead is not progressing so you don't want to qualify it to become an Opportunity but you want to transfer selected data to a new Contact record for marketing purposes and want to transfer information to the new Contact - e.g. source, tags etc and then remove the original Lead.