---
title: "Flat File Integration for Custom CRM and MAP Platforms"
slug: "flat-file-integration-for-custom-crm-and-map-platforms"
description: "Integrate your CRM/MAP with 6sense using flat files for secure data syncing, ensuring compliance and leveraging AI-driven Data Taxonomy for enhanced insights."
tags: ["Data Requirement", "Flat File Integration", "Integrations and APIs", "Metadata Requirement", "Metadata Requirements", "SFTP Data Sync"]
updated: 2026-08-11T11:27:28Z
published: 2026-08-11T11:27:28Z
canonical: "support.6sense.com/flat-file-integration-for-custom-crm-and-map-platforms"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.6sense.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Flat File Integration for Custom CRM and MAP Platforms

This guide outlines the high-level scope and prerequisites for integrating your CRM or MAP with 6sense using a flat file approach, particularly if your system is not natively supported in 6sense.

The flat file integration allows customers to sync data from their internal CRM/MAP platforms into 6sense via secure SFTP. This method ensures flexibility while maintaining data consistency and integrity.

> [!NOTE]
> Note: Customers using a flat-file MAP integration can now use AI-driven Data Taxonomy to classify and map MAP data. Previously, this capability was available only for CRM data.

### Prerequisites

Before initiating integration, ensure the following requirements are met:

- **Data Requirement Compliance:** Data must follow the schema defined in our data requirement as mentioned below.
- **SFTP Setup:**
  - Data should be uploaded to the 6sense SFTP location at the agreed time in the contract.
  - Customers should send the flat file data to the SFTP location specified by 6sense. They can obtain the SFTP endpoint details from their CSM or Product Consultant
- **Daily File Push:** Upload your flat files to the SFTP location daily at the specified time as per your contract.
- **Metadata Requirement:** If you’re sending data for Lead, Contact, Opportunity, or Account objects, you must also include the corresponding metadata file. Refer to the Metadata requirement for more details.
  - Data should be restricted to only following data types:
    - String
    - Picklist
    - Combobox
    - Textarea
    - Reference
    - Url
    - ID
    - Phone
    - Email
    - Multipicklist
    - Datetime
    - Date
    - Address
    - Double
    - Currency
    - Boolean
    - Int
    - Percent

## Data requirement

- Customers must map their internal objects from their CRM/MAP to the minimum object requirements specified for their ABM and Sales Intelligence plans.
- We recommend that the customer provide the data in the following specified format for all the mandatory objects.

### Recommended file format

- **File Type**: CSV
- **File Naming Convention:**
  - YYYYMMDD_YYYYMMDD_CUSTOMERNAME_CRM_OBJECT.csv
  - **Example**: 20171101_20190607_ABC_CRM_CONTACT.csv
- **Data Source Name(Internal to 6sense):**
  - Note: This section is only relevant for the Product Consultant or Adoption Consultant from the 6sense team who is configuring the Flat File for customers. Customers do not need to be concerned with this data source.
    - For Account object: {org_name}_crm_account
    - For Contact object: {org_name}_crm_contact
    - For Lead object: {org_name}_crm_lead
    - For Opportunity object: {org_name}_crm_account
    - For Account Team Member object: {org_name}_crm_account_team_member

### Sample data structure

| **File type:** csv |
| --- |
| **File name format:** YYYYMMDD_YYYYMMDD_CUSTOMERNAME__CRM_CONTACT.csv |
| **Sample file name:** [20171101_20190607_CUSTOMERNAME _CRM_CONTACT.csv] |

| **id** | **contactname** | **country** | **city** | **modifieddate** | **Create date** |
| --- | --- | --- | --- | --- | --- |
| 123456 | David | USA | Tempe | 12/12/2020 | 12/12/2020 |
| 723456 | Joseph | India | Delhi | 13/8/2020 | 13/8/2020 |
| 444343 | Timur | Spain | Madrid | 8/9/2020 | 8/9/2020 |
| 943456 | Rishi | USA | Clifton | 03/7/2020 | 03/7/2020 |
| 833545 | Abhi | USA | Las Vegas | 02/8/2020 | 02/8/2020 |
| 566565 | Justin | India | Pune | 28/2/2020 | 28/2/2020 |
| 782828 | Riyaz | USA | Seattle | 16/4/2020 | 16/4/2020 |
| 345666 | Steven | USA | Bristol | 9/3/2020 | 9/3/2020 |

## Metadata requirement

Metadata is required for creating filters, displaying information on Sales Intelligence dashboards, and is also used in predictive modelling. Customers are expected to provide this information, in addition to data drops, to help us understand the structure of their data and any changes to it (such as column deletions or data type modifications).

### When to send Metadata

- **Initial Onboarding**: When you first upload data to 6sense.
- **Schema Changes:** Any changes to your object schema, such as:
  - Data type modifications.
  - Column deletions or additions.

> [!NOTE]
> **Note**: If there’s no change in your schema, you do not need to resend the metadata file. 6sense will assume the existing metadata is still valid.

### Required objects

Metadata must be provided for:

- Lead
- Contact
- Account
- Opportunity
- Account Team Member

### Metadata file format

- **File Type**: csv
- **File Naming Convention:**
  - objectname_metadata.csv
  - **Example**: contact_metadata.csv

### Sample Metadata structure

| **File type:** csv |
| --- |
| **File name format :** objectname_metadata.csv |
| **Sample file name:** [lead_metadata.csv] |

| **FieldName** | **Data Type** | **Metadata** | **isdeleted** | **label** |
| --- | --- | --- | --- | --- |
| id | int |  | FALSE | Lead ID |
| firstname | string |  | FALSE | First Name |
| lastname | string |  | FALSE | Last Name |
| email | string |  | FALSE | Email ID |
| jobtitle | string |  | FALSE | Job Title |
| createddate | date |  | FALSE |  |
| modifieddate | date |  | FALSE |  |
| accountid | string |  | FALSE | Account ID |
| country | string |  | FALSE | Country |
| department | string |  | FALSE |  |
| leadsource | string |  | FALSE |  |
| decisionrole | string |  | TRUE |  |
| jobfunction | string |  | FALSE |  |
| phone | long |  | FALSE |  |
| nolongeratcompany | string |  | FALSE |  |
| donotcall | string |  | FALSE |  |
| donotemail | string |  | FALSE | Email of Lead |
| state | string |  | FALSE | State/Province |
| city | string |  | FALSE | City |
| address | string |  | FALSE | Address |
| zip | int |  | FALSE | Zip/Postal Code |
| ownerid | reference | {“reference”: [“User”]} | FALSE | Owner ID |

### Metadata field descriptions

| **Field** | **Description** |
| --- | --- |
| Field Name | Column Name in CRM/MAP data |
| label | Display Name of the field |
| IsDeleted | Marks if the column has been removed in your system |
| Metadata | Used when a field refers to another object (e.g., ownerid referencing “User”) |
| Datatype | Accepted types: string, int, long, float, boolean, reference |

## Sample File

A template file is attached for your reference, which can be downloaded.

Customer Relationship Management, an external platform used to manage your relationships and interactions with potential customers and clients.

Marketing Automation Platform, a 3rd-party platform that automates your marketing tasks and workflows, allowing for more efficient marketing campaigns.

Account-Based Marketing, the former name of the 6sense Revenue Marketing product.

The name of our product that provides insights and analytics to help you improve your sales strategies and decision-making.

Comma-Separated Values, a file format used to store tabular data in plain text, where each line corresponds to a row in the table and each value is separated by a comma.

## Attachments

- [Template_FileSpec_Flatfile_Integration.xlsx.zip](https://cdn.us.document360.io/0e2cd0a2-b3b3-495b-80df-96f8381febea/Images/Documentation/Template_FileSpec_Flatfile_Integration.xlsx.zip)