Detailed Explanation of thdata Export Formats: How to Import CSV/TXT Results into CRM? A Comparison Guide with KK-DATA

In overseas marketing and B2B SaaS lead generation scenarios, the export format of the screening platform directly determines the efficiency and accuracy of subsequent CRM import. Whether it’s Salesforce, HubSpot, or Zoho, incompatible formats or encoding issues can lead to data loss, field misalignment, or garbled text. This article will start from the details of thdata export formats, compare KK-DATA’s multi-format export capabilities, and provide best practices for the entire process from screening results to CRM import, helping your operations team avoid common pitfalls.

What export formats does thdata support for screening results? — Differences between CSV and TXT

As a type of screening tool, thdata typically offers two basic export formats: CSV and TXT. While both can save numbers and status information, there are significant differences in practical use:

• Field structure: CSV uses commas (,) to separate fields and can contain multiple columns (e.g., phone number, activation status, activity label); TXT may be a plain text list with one number per line, with fewer fields or no delimiters.
• Delimiter: CSV defaults to comma separation; some regions use tabs. TXT usually has no fixed delimiter and requires manual parsing.
• Encoding: Most thdata platforms export in GBK or ANSI encoding, rather than the universal UTF-8 or UTF-8 with BOM. This easily causes garbled Chinese characters when interfacing with overseas CRMs (e.g., Salesforce, HubSpot).
• Compatibility: CSV can be opened directly by Excel and Google Sheets, but CSV encoded in GBK cannot display properly on Mac or Linux environments. TXT requires manual “Import → Split Columns” operations.

Practical impact: If your downstream tool is an overseas CRM or data middle platform, UTF-8 encoded CSV is the safest choice. However, thdata’s default export format often requires secondary encoding conversion, increasing data cleaning costs.

KK-DATA’s multi-format export and CRM integration capabilities

KK-DATA has made targeted optimizations in the export stage. It not only supports CSV and TXT but also allows users to customize export fields, delimiters, and encoding methods, reducing intermediate data transfer steps.

Detailed steps of KK-DATA export

From submitting a screening task to final CRM import, KK-DATA provides a standardized operation path. Here are the complete steps:

1. Log in to the console (https://app.kkdata.cc/) and top up the balance – ensure sufficient account balance. Billing is per record, no subscription plan.
2. Create a screening task – Select the platform (Telegram / WhatsApp / iMessage / RCS, etc.), country, or custom number file, and set detection types (e.g., activation detection, activity, gender identification).
3. Wait for task completion – The system processes automatically. You can receive notifications via Telegram after completion.
4. Select export fields – On the task details page, check the columns you need to export: Phone number, tmid/wsid, activity label (e.g., 7 days / 15 days / 30 days), gender label (Male / Female / Unknown), platform status (Active / Valid / Invalid).
   Note: The fewer fields, the faster the export speed. It is recommended to select only the columns truly needed by the downstream CRM.
5. Choose format and encoding – Select CSV or TXT. Default encoding is UTF-8 with BOM (compatible with most SaaS CRMs). You can also switch to UTF-8 without BOM or GBK.
6. Download the file – The exported file can be used directly without secondary cleaning.
7. Import into CRM – Use the CRM’s native import function (e.g., Salesforce’s “Data Import Wizard”, HubSpot’s “Import Contacts”) and map fields accordingly.

Export field description and CRM field mapping

To allow the CRM to accurately identify each record, it is recommended to establish corresponding custom fields in advance. Here is an example of common field mapping:

Screening Export Field	CRM Custom Field	Data Type	Notes
Phone Number	Phone Number	Text/Phone	Primary key, unique identifier
tgid	Telegram ID	Number	Prevents duplicate imports
wsid	WhatsApp ID	Number	Used for message push
Activity Label	Activity Score / Active Status	Option (7 days/15 days/30 days)	Used for tiered operations
Gender Label	Gender	Option (Male/Female/Unknown)	Used for precise messaging
Platform Status	Platform Status	Option (Active/Valid/Invalid)	Filters invalid numbers

Mapping tips: Before CRM import, open the exported CSV in Excel or Google Sheets to confirm the field order matches the CRM template. KK-DATA supports customizing the export column order, which can be adjusted in advance.

Comparison of thdata and KK-DATA in export capabilities

To help users make quick decisions, the following objective comparison is made from four core dimensions (judgment based on each platform’s public information and actual console interface):

Dimension	thdata	KK-DATA
Export Formats	CSV, TXT (basic)	CSV, TXT (customizable columns and encoding)
Field Richness	Fixed fields (e.g., phone number, activation status)	Custom fields: tgid, wsid, activity (7/15/30 days), gender, platform status, etc.
Encoding Compatibility	Mostly GBK/ANSI	UTF-8 with BOM / UTF-8 / GBK (selectable)
Success Rate of CRM Integration	Requires secondary encoding conversion, prone to garbled text	One-time export, directly importable, compatible with most SaaS CRMs

Format support and field customization

• thdata usually only provides basic field exports, such as “phone number + status”. If you need tgid, wsid, or gender labels, you may not be able to obtain them directly, or you may need to create additional tasks.
• KK-DATA allows you to select detection types when creating a task (e.g., “tg valid + tg active + gender identification”) and independently check columns during export without repeated filtering. For example, you can export only numbers with “activity ≥15 days and gender = male”, generating a CSV with only the required fields, reducing subsequent cleaning work.

Practical experience in CRM integration

Real scenario: A business team exported CSV from thdata and found garbled Chinese characters when importing into Salesforce (due to GBK→UTF-8 conversion issues). They had to manually open the file in Notepad, save it as UTF-8, and adjust delimiters, spending 20 minutes processing 5000 records. In contrast, with KK-DATA, exporting the same amount of data took only 30 seconds (default UTF-8 with BOM), and direct import into Salesforce achieved a 100% success rate.

Best practices for the entire process from screening results to CRM import

To maximize the value of the data, it is recommended to follow these steps:

1. Priority format: CSV (UTF-8 with BOM): Best compatibility, avoids garbled text.
2. Keep fields lean but complete: Only check fields that already exist in or can be mapped to your CRM. If tgid is missing, consider creating a custom field in CRM.
3. Deduplicate and clean: Before import, use Excel or Google Sheets’ “Remove Duplicates” function, or use KK-DATA’s built-in data deduplication repository, to avoid duplicate imports.
4. Import in batches: If data volume exceeds 100,000 records, split into 2-5 CSV files and import in batches to reduce CRM timeout risk.
5. Verify import results: After import, check the total number of phone numbers and label distribution in the CRM, and cross-validate with the original export list.

Frequently Asked Questions (FAQ)

Q: The CSV exported from thdata shows garbled text in Salesforce, what should I do?

A: Garbled text is usually caused by encoding incompatibility. Solutions:

1. Confirm the encoding of the file exported from thdata (open in Notepad; see if it says “ANSI” or “UTF-8” at the bottom right).
2. If it’s GBK/ANSI, first save it as UTF-8 using Notepad (may lose BOM).
3. Better yet, directly use KK-DATA to export in UTF-8 with BOM format, which is ready to go.

Q: Which platform, KK-DATA or thdata, offers more export fields?

A: Please refer to the actual console display of each platform. KK-DATA supports additional fields like tgid, wsid, activity (7/15/30 days), gender, etc., and allows customizing export columns. thdata usually only provides basic fields (phone number, activation status). It is recommended to choose based on the fields required by your CRM.

Q: How to import the exported TXT file into Excel?

A: Steps:

1. Open Excel → Click “Data” → Import from Text/CSV.
2. Select the file, set encoding to UTF-8 (if garbled, choose GBK).
3. Choose delimiter as comma or tab (depending on the actual TXT format), preview and ensure correctness, then import.

Q: Can KK-DATA directly connect to Salesforce?

A: It does not support direct API integration, but you can export CSV/TXT and then import via Salesforce’s native data import feature (e.g., Data Import Wizard) or third-party automation tools (e.g., Zapier) indirectly. For details, refer to the KK-DATA User Documentation.

Q: After exporting from thdata, the phone number formats are inconsistent. What should I do?

A: Common issues include numbers with “+86” prefix or spaces. Solutions: Use “Find and Replace” in Excel to remove spaces, then use the formula =SUBSTITUTE to remove the ”+” sign (if the CRM does not accept international format). When exporting from KK-DATA, you can set a unified format (e.g., E.164 international format) in the console to reduce post-processing work.

Summary and Action Recommendations

Thdata export formats can meet basic needs but have room for improvement in field richness, encoding compatibility, and CRM integration experience. KK-DATA, through custom fields, diverse encoding options, and a seamless export process, significantly reduces the intermediate cost from screening results to CRM import.

If your team frequently performs large-scale number screening and imports into customer management systems, we recommend:

• First register and experience the KK-DATA console: https://app.kkdata.cc/
• Refer to more detailed export and CRM integration tutorials: https://docs.kkdata.cc/
• For special field requirements or bulk issues, contact customer service directly via Telegram: @kkdata_cc

Let data flow more smoothly and focus on real lead generation growth, not data cleaning.