InCountry logo
mobile-nav
Search
  • Products
    • Platform
      • Overview
      • Compliance and security
      • How it works
      • For SaaS
      • For internal apps
    • Gateways
      • Email
      • HTML
      • Payments
      • Web Forms
  • Solutions
    • Energy
    • Financial services
    • Healthcare
    • Retail
    • Technology
  • Integrations
    • SaaS
      • Cegid
      • Intertrust
      • Mambu
      • PayPal
      • Salesforce
      • Segment
      • ServiceNow
      • Stripe
      • Twilio
      • Veeva Systems
    • IAAS
      • InCountry on Alibaba Cloud
      • InCountry on Yandex.Cloud
  • Resources
    • Country compliance
    • Documentation
    • Library
    • Partners
    • Pricing
  • About
    • Blog
    • Careers
    • Contact Us
    • FAQ
    • Leadership
  • Login
  • Schedule a Demo

›User's guide

Home
  • InCountry Platform
Portal
  • Getting started
  • Documentation
    • Dashboard
    • Managing environments
    • Managing clients and integrations
    • Managing Border configuration
    • Managing serverless scripts
    • Managing file imports
    • Managing profile and organization
    • Managing users
    • Managing secret keys
    • Managing recommendation modules
    • Managing subscription
  • Release notes
Border
  • Documentation
  • Release notes
REST API
  • Documentation
  • How to test CRUD requests through REST API
  • Release notes
Serverless
  • Documentation
Salesforce
  • About
  • Overview
  • Quick start guide for three-model package
  • Quick start guide for legacy package
  • Administrator's guide
    • Managing the package
    • Managing permissions
    • Managing OAuth2 authentication and authorization
    • Managing certificates
    • Registering CSP Trusted Sites
    • Managing InCountry Endpoints
    • Managing REST endpoints
    • Managing InCountry flags
    • Loading the application
    • Managing data regulation policies
    • Managing protected fields
    • Hashing the UserName field
    • Managing custom objects
    • Replacing standard elements
    • Configuring record search
    • Managing components
    • Setting up Salesforce Experience Cloud
    • Managing serverless functions
    • Managing InCountry cache
    • Managing Apex triggers
    • Managing record synchronization
    • Using Email-to-Case feature
    • Debugging
  • Developer’s guide
    • Apex SDK
    • JavaScript API
    • Retrieving record statistics
    • Tracking field history
  • User's guide
    • Working with protected fields
    • Sending compliant email messages
    • Importing data into Salesforce
    • Migrating records
    • Managing audit reports
    • Converting leads
    • Managing reports
    • FAQ
    • Release notes
Payment Vault
  • Documentation
BYOK
  • Documentation
FAQ
  • How to use the InCountry platform
  • Integration options
  • Data regulation models
  • Limits and quotas
  • Video tutorials
Service Status
  • Status

Converting leads

note

Conversion of leads is supported in the legacy package and in the three-model package for the redaction and restrictions models.

The Lead Convert component converts a lead into an account and contact, as well as an opportunity.

To convert a lead:

  1. On the Leads tab, open the lead record.

  2. At the top right part of the page, click Convert.

    Convert

  3. In the Convert Lead form, define the type of record you want to convert the current lead into.

    Define the type of record

  4. In the Account section, select Create New and enter the account name if you want to convert your lead into an account, or select Choose Existing and pick the appropriate account for lead conversion.

  5. In the Contact section, select Create New and enter the contact name if you want to convert your lead into a contact, or select Choose Existing and pick the appropriate contact for lead conversion.

  6. In the Opportunity section, select Create New and enter the opportunity name if you want to convert your lead into an opportunity, or select Choose Existing and pick the appropriate opportunity for lead conversion. You can also choose the Don’t create an opportunity upon conversion option if you don't want to create an opportunity.

  7. Verify the record owner and converted status in the corresponding fields.

  8. Click Convert.

note

Please take into account the following points:

  1. A lead can be converted to regulated and non-regulated objects.

  2. The lead must always be a regulated object.

  3. To convert a lead to other objects in other countries, the user must have access to this country. (For example,

    1. A user OUTSIDE OF the country treated under the redacted policy cannot convert a record to the lead pertaining to the country managed under the redacted policy.

    2. A user FROM the country treated under the redacted policy can convert a lead to the record that can be attributed to the country treated under the redacted policy and to the record that can be treated under the restricted or replicated policy.

  4. To convert a lead record according to the applied record policy, the lead record pending conversion must have a record-level policy applied.

Converting leads in the tree-model package

In order for the leads to be converted according to the record level policy, it is mandatory to map the compound fields in Setup (country, address, city, state and so on) with the Lead, Account, Contact and Opportunity fields.

  1. From Setup, select Custom Metadata Types.

    Custom Metadata Types

  2. Click Manage Records next to InCountry Lead Convert Mapping.

    Manage Records

  3. To add a compound field (e.g. country field), click New.

    New

  4. Add other compound fields as shown above.

    note

    Compound fields are comprised of several fields (so-called constituents), for example the Address field includes the City, Zip code, State, and other fields. When converting, all these fields should be matched between the source Salesforce object and the target Salesforce object. You need to add the logic for each constituent of the compound Address field for all Salesforce objects which a lead can be converted to.

    To do this, it is necessary to add a new item to the Lead Convert Mapping. For EACH constituent of the compound Address field, you need to create a new item.

    When creating, you need to specify the API name of the field on the lead object. To get API names of fields, navigate to Object Manager, open the related Salesforce objects and on the Fields and Relationships tabs you can find the API names for required fields. These fields will take values from the lead record passing through conversion.

  5. From Setup, select Object Manager.

  6. Select Lead.

    Select Lead

  7. Select Fields & Relationships.

    Select Fields and Relationships

  8. In the top right part of the screen, click Map Lead Fields.

  9. Use the tabs (Account, Contact or Opportunity) to map each of your organization's custom lead fields to one of your custom account, contact, or opportunity fields.

    Map the fields

  10. Click Save.

← Managing audit reportsManaging reports →
  • Converting leads in the tree-model package
InCountry logo blue
© InCountry 2022.
All rights reserved. InCountry, Inc
  • PRIVACY POLICY
  • TERMS OF SERVICE
  • Social share
    • YouTube logo
    • Facebook logo
    • Twitter logo
    • LinkedIn
  • Column 1
    • Products
      • Platform
        • Overview
        • Compliance and security
        • How it works
        • For SaaS
        • For internal apps
      • Gateways & Vaults
        • Email
        • HTML
        • Payments
        • Web Forms
    • Solutions
      • Energy
      • Financial services
      • Healthcare
      • Retail
      • Technology
  • Column 2
    • Integrations
      • SaaS
        • Cegid
        • Intertrust
        • Mambu
        • PayPal
        • Salesforce
        • Segment
        • ServiceNow
        • Stripe
        • Twilio
        • Veeva Systems
      • IAAS
        • InCountry on Alibaba Cloud
        • InCountry on Yandex.Cloud
  • Column 3
    • Resources
      • Country compliance
      • Documentation
      • Library
      • Partners
      • Pricing
    • About
      • Blog
      • Careers
      • Contact Us
      • FAQ
      • Leadership