Complete Tutorial for Migrating Number Screening from thdata to KK-DATA: List Format, Task Creation, and Export Field Mapping Guide

Many overseas marketing teams initially choose thdata for Telegram and WhatsApp number screening. However, as business scales up, requirements for detection dimensions, data accuracy, and billing flexibility increase. If you’re considering migrating your screening workflow from thdata to KK-DATA, this article will walk you through the entire process—from list format conversion, console task configuration to export field mapping—along with a practical migration checklist.

Why Consider Migrating Number Screening from thdata—Key Platform Differences

Before migrating, objectively comparing thdata and KK-DATA in terms of features, billing, and user experience will help you evaluate the value of migration.

Feature Coverage and Detection Type Comparison

Detection Type	thdata	KK-DATA
Telegram Registration Check (Registration Verification)	Supported	Supported
Telegram Validity Check (Recent Login)	Partially supported (no active window)	Supported (specify 7/15/30-day active window)
Telegram Activity Check	—	Supported, filterable by day
Telegram Gender Recognition (Avatar Recognition)	—	Supported, export gender labels
Telegram tgid Export	—	Supported
WhatsApp Validity Check	Supported	Supported, export wsid
iMessage / RCS / Invalid Number Detection	—	Supported (subject to console availability)
Data Deduplication	Manual handling required	Built-in cross-task deduplication repository

KK-DATA additionally provides deep fields like active windows, gender recognition, tgid/wsid export, which are more useful for granular operations (e.g., segmenting by activity level, targeting specific genders).

Billing Model and Task Scale

Please refer to thdata’s official website for its billing method. KK-DATA uses a no-subscription, pay-per-record balance deduction model—no prepaid packages required, pay only for what you use. A single task supports up to approximately 1 million numbers, and the estimated cost is clearly displayed before submission. Insufficient balance prevents submission. Recharge via USDT (TRC20), minimum around 50 USDT. Balance updates automatically upon receipt, with no expiration.

Pre-Migration Preparation—Exporting thdata Old Lists and Confirming Format

First, export your existing number list from the thdata backend. Usually, you can export as CSV or TXT files. Check that the fields include:

Phone number (with country code)
Original platform identifier (e.g., Telegram/WhatsApp)
Existing detection results (optional, for later comparison)

Common format issues: numbers may lack the + sign, contain spaces or parentheses, or have inconsistent country code prefixes (e.g., 86 mixed with +86). The conversion step will handle these uniformly.

Cleaning and Deduplication: Using KK-DATA Data Deduplication Repository

Duplicate numbers often appear in migration lists. Submitting them directly to a screening task wastes detection balance. KK-DATA provides a data deduplication repository feature. You can import your old list into this repository, and the system automatically identifies duplicate numbers across tasks, keeping only unique records. Then create screening tasks based on the deduplicated list to avoid redundant detection.

Get Latest Platform Unit Prices and Recharge

Visit KK-DATA Billing Page to view real-time unit prices for each platform and detection type. Since prices may change, refer to the console for the latest rates. After confirming prices, recharge your account using USDT (TRC20). We recommend an initial recharge of at least 50 USDT to ensure your first tasks run smoothly. Your old thdata balance cannot be transferred; please use up your old platform balance before switching.

List Format Conversion—From thdata Format to KK-DATA Compatible Format

KK-DATA accepts numbers in one number per line, preferably in international format: +[country code][number]. For example, a Chinese number: +8613800138000. thdata may export in formats such as:

Plain digits (e.g., 8613800138000 or 13800138000)
Comma-separated (e.g., 86,13800138000)
With spaces or parentheses (e.g., +86 138 00138000 or (86)13800138000)

Conversion Steps:

Open the exported file in Excel or a text editor (e.g., VS Code, Notepad++).
Remove extra spaces, parentheses, and hyphens.
Ensure all numbers start with + and have the correct country code (e.g., +86 for China).
If thdata exported plain digits that include the country code, simply add + at the beginning; if only local numbers, you need to prepend the country code.
Save as a UTF-8 encoded TXT or CSV file.

Format Tip

It’s recommended to unify all numbers into international format (+country code + number) without spaces or parentheses. KK-DATA’s global number generation module automatically handles country code recognition, but using a unified format for upload increases task success rate.

After conversion, test with a small sample (e.g., 100 numbers) to ensure the format is correct before submitting the full task.

Creating Screening Tasks in KK-DATA Console—Platform-Specific Operations

Select Platform: Telegram, WhatsApp, iMessage, RCS, etc. (based on actual console list).
Upload List: Upload the converted TXT/CSV file.
Select Detection Type: Check the required detection items per platform (see platform-specific instructions below).
Name the Task: Include date, platform, and type for easy traceability later.
Confirm Estimated Cost: The system automatically calculates the estimated cost based on number count and detection types. Insufficient balance will trigger a prompt.
Submit Task: Wait for detection to complete. You can enable Telegram notifications (configure in settings) to receive alerts upon completion.

Ensure Sufficient Balance

Before submitting, the system calculates the estimated cost. Insufficient balance prevents submission. We recommend recharging at least 50 USDT before creating your first task.

Telegram Screening Task—Activity Windows and Gender Recognition

Telegram screening is one of the most commonly used features for overseas marketing teams. KK-DATA offers multi-level detection. You can check multiple types in a single task:

tg Registration (Registration Check): Determines if a number is registered on Telegram. Basic detection.
tg Valid: Checks if the number has recent login activity. More precise than “Registration”.
tg Active: Allows specifying an active window, e.g., active in the last 7 days, 15 days, or 30 days. Useful for filtering high-activity users.
telegram Gender: Infers gender through avatar recognition (results are for reference, not 100% accurate).
tgid Export: When checked, the exported results will include the Telegram ID (tgid) for each number, useful for precise follow-up.

Recommendation: For the first migration, check all options to export full fields and compare with thdata results. After confirming accuracy, subsequent tasks can check only “Valid + Active” as needed.

WhatsApp Screening Task—Validity Check and wsid Export

WhatsApp screening is mainly used to confirm whether a number is registered on WhatsApp and to obtain the wsid (WhatsApp user identifier). Steps:

Select platform “WhatsApp”.
Check detection type “whatsapp valid”.
Optionally check “wsid export”. Successfully detected numbers will include wsid, which can be used for secondary verification or re-following.

Note: WhatsApp detection results are “Valid” (registered) or “Invalid” (not registered). Invalid numbers are not charged. When exporting, you can choose to export only valid numbers to reduce post-processing costs.

Export Results and Field Mapping—thdata Export Fields vs. KK-DATA Fields

The corresponding field names between thdata and KK-DATA are as follows:

thdata Field (Example)	KK-DATA Field	Description
Phone Number	phone	International format, includes +
Registration Status	telegram_registered	Boolean, true/false
Last Active Time	telegram_last_active	Timestamp format
Validity (Login)	telegram_valid	Logged in within the last 30 days
Activity (7 days)	telegram_active_7d	Output only when active window is checked
Gender	telegram_gender	male/female/unknown
Telegram ID	telegram_tgid	Output only when tgid export is checked
WhatsApp Registration Status	whatsapp_valid	Boolean
WhatsApp ID	whatsapp_wsid	Output only when wsid export is checked

KK-DATA supports export in CSV and TXT formats. On the export page, you can select the desired fields and apply filters (e.g., export only numbers marked as “tg valid”, or only numbers with gender “female”).

Export Best Practice

For the first migration, we recommend exporting all fields (including invalid numbers) to verify accuracy by comparing with thdata old results. For subsequent tasks, export only valid/active numbers to save storage and processing time.

Post-Migration Verification and Process Solidification (Checklist)

After completing the first batch of tasks, check against the following list to ensure a smooth platform migration:

Consistency Verification: Run the same batch of numbers through both thdata and KK-DATA separately, comparing the detection rate of valid numbers. Some variance is acceptable (due to interface response differences), but significant discrepancies require investigation.
Export Fields Meet Business Needs: Verify that all required fields (tgid, wsid, gender, activity) are correctly exported and in a directly usable format.
Telegram Notification Working: Configure Telegram notifications in the console settings (requires linking your account), submit a test task, and confirm you receive a completion alert.
Data Deduplication Effectiveness: Import the old list into the deduplication repository first, then create a task. Check that duplicate numbers are filtered out and no extra charges incurred.
Routine Workflow Handover: Document the steps “Export list → Format conversion → Upload → Create task → Export results” and train team members. Note that the console task logging feature records every operation for easy traceability.

Frequently Asked Questions

Q: Do I need to re-clean my old list when migrating from thdata to KK-DATA?
A: It is recommended to use KK-DATA’s data deduplication repository to deduplicate your old list before creating screening tasks. For number format, just ensure it’s in international format (e.g., starting with +86). No additional conversion is needed. KK-DATA supports batch upload of TXT/CSV files.

Q: Which platform has higher screening accuracy, thdata or KK-DATA?
A: Accuracy depends on the number sample, detection time, and platform response. KK-DATA’s Telegram screening supports multiple dimensions (registration/valid/active/gender) and connects to platform interfaces in real time. We recommend testing the same batch of numbers on both platforms and comparing the results. Let the actual detection data speak.

Q: Can KK-DATA detect more than 1 million numbers at once?
A: A single task supports up to approximately 1 million numbers. For larger scales, submit tasks in batches. KK-DATA’s deduplication repository automatically handles cross-task deduplication to avoid double charging.

Q: I still have balance in my old thdata account. Can I transfer it to KK-DATA?
A: No direct transfer is possible. KK-DATA independently uses USDT (TRC20) recharge, minimum around 50 USDT. You can use up your old platform balance before starting migration tasks on KK-DATA. Recharged balance never expires, deducted per record.

Ready to migrate? Log in to KK-DATA Console now to create your first screening task.
View full documentation: Documentation | Billing: kkdata.cc/billing/
Have questions? Contact support via Telegram: @kkdata_cc

Complete Tutorial: Migrating Phone Number Screening from thdata to KK-DATA – List Format, Task Creation, and Export Field Mapping Guide

关于作者