---
schema_version: "1"
id: 68c01e8d76de218f13845c7d750cb9b2a153b5dab2b45cad8b590b03376c1eb0
title: DataImportManagementSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_dataimportmanagementsettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_dataimportmanagementsettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 4b3251a4a0fe9e98f640089285f049a0bff0545e65bdfe924ed7d81ee41bf576
description: Represents an org's contact and leads import settings.
---
# DataImportManagementSettings

Represents an org's contact and leads import settings.

## Parent Type and Manifest Access

This type extends the [Metadata](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/metadata.htm "The base class for all metadata types. You can’t edit this object. A component is an instance of a metadata type.") metadata type and inherits its fullName field.

In the package manifest, all the settings metadata types for the org are accessed using the “Settings” name. See [Settings](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_settings.htm "Represents the organization settings related to a feature. For example, your password policies, session settings and network access controls are all available in the SecuritySettings component type.") for more details.

## File Suffix and Directory Location

DataImportManagementSettings values are stored in the DataImportManagement.settings file in the settings folder. The .settings files are different from other named components, because there is only one settings file for each settings component.

## Version

DataImportManagementSettings components are available in API version 57.0 and later.

## Special Access Rules

DataImportManagementSettings is available when your org enables the DataImportManagement permission, which is only available for particular editions.

## Fields

| Field Name | Description |
| --- | --- |
| enableEasyImport | 
Field Type

boolean

Description

Indicates whether Basic Data Import is enabled (true) or not (false). When true, users are guided step by step to select how they want to import contacts and leads to Salesforce.



 |

## Declarative Metadata Sample Definition

The following is an example of a DataImportManagementSettings component.

<?xml version="1.0" encoding="UTF-8"?>
<DataImportManagementSettings xmlns="http://soap.sforce.com/2006/04/metadata">
          <enableEasyImport\>true</enableEasyImport\>
</DataImportManagementSettings\>

The following is an example package.xml that references the previous definition.

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
          <types\>
               <members\>DataImportManagement</members\>
               <name\>Settings</name\>
          </types\>
          <version\>57.0</version\>
</Package\>

## Wildcard Support in the Manifest File

The wildcard character \* (asterisk) in the package.xml manifest file doesn’t apply to metadata types for feature settings. The wildcard applies only when retrieving all settings, not for an individual setting. For details, see [Settings](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_settings.htm "Represents the organization settings related to a feature. For example, your password policies, session settings and network access controls are all available in the SecuritySettings component type."). For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/file_based_zip_file.htm "The deploy() and retrieve() calls are used to deploy and retrieve a .zip file. Within the .zip file is a project manifest (package.xml) that lists what to retrieve or deploy, and one or more XML components that are organized into folders.").