Migrating from 007data/thdata to KK-DATA: A Complete Platform Migration Guide (Switching Number Screening Tools Guide)
关于作者
KK-DATA 获客数据筛号平台官方内容团队。
Migrating from 007data/thdata to KK-DATA: Complete Platform Migration Guide (Phone Number Screening Tool Switching Guide)
In overseas marketing and Telegram/WhatsApp community promotion scenarios, phone number screening tools are a core component of data operations. Many teams have long used established platforms like 007data or thdata, but as business scales grow or functional requirements change, they begin considering migrating to more flexible, feature-rich solutions. KK-DATA, as a screening platform that charges per number, supports multi-platform detection, and includes a built-in deduplication repository, is becoming the migration destination for an increasing number of users. This article will walk you through the complete steps for switching from 007data/thdata to KK-DATA, ensuring seamless integration of number data and screening workflows, and providing best practices for cost control and continuous customer acquisition.
Why Migrate from 007data/thdata to KK-DATA?
Before deciding to migrate, understanding the core differences between the two platforms will help you evaluate whether the switch is worthwhile. Below is an objective comparison across three dimensions: detection capabilities, billing models, and console experience. We do not disparage competitors—only state the actual differences.
Feature Comparison: Detection Types & Efficiency
| Dimension | 007data/thdata (Common Case) | KK-DATA |
|---|---|---|
| Telegram Detection | Mostly supports active/valid detection | Supports: active, valid, activity level (7/15/30-day window selectable), gender identification (based on avatar), tgid export |
| WhatsApp Detection | Usually only supports valid number detection | Supports valid detection, wsid export |
| Other Platforms | May be limited to basic number verification | Supports iMessage, RCS, invalid number, carrier detection (based on what’s available in the console) |
| Max Numbers per Task | Depends on plan, often with fixed limits | Up to approximately 1 million, flexibly adaptable to large tasks |
| Export Fields | Typically includes number and detection result | Can export number, detection result, activity status, gender, tgid, wsid, and more |
KK-DATA offers richer detection dimensions, especially Telegram activity windows, gender identification, and tgid/wsid export. This is particularly valuable for teams requiring granular operations (e.g., targeted push by gender, tiered activity-based campaigns).
Billing Differences: No Subscription vs. Fixed Plans
007data/thdata typically uses a subscription plan model: a fixed monthly fee for a certain amount of detection credits, with overages requiring additional payment or a plan upgrade. This model can be friendlier for high-frequency users with stable usage within the plan range, but it is less flexible for teams with fluctuating usage (wasting credits during low seasons, incurring high costs during peak seasons).
KK-DATA uses a pay-per-number, no subscription model: first deposit USDT (TRC20) into your balance; when submitting a task, preview the estimated cost; after the task completes, the fee is deducted from the balance. Pay for what you use, and the balance never expires. For small teams with low or fluctuating usage, or those wanting to control cash flow, this model is more hassle-free. Additionally, anonymous USDT deposits avoid exposing sensitive information through traditional payment channels.
Pre-Migration Preparation: Organize Existing Resources & Confirm Compatibility
The first step in migration is not to register on the new platform directly, but to organize data assets from the old platform and confirm format compatibility.
Export Data Inventory from Old Platform
Log in to the 007data or thdata backend and perform the following exports:
- Already-screened number results: includes valid numbers, tgid, wsid, detection status, etc. Save as CSV or TXT.
- Unscreened number lists: raw number files not yet submitted for detection.
- Historical task records: if the platform provides task export functionality, archive task IDs, detection times, and other information for backup.
After exporting, it is recommended to organize files by platform and detection type, and keep a local backup.
Verify KK-DATA Supported File Formats & Fields
KK-DATA’s “Global Number Screening” module accepts CSV and TXT files, requiring one number per line. If the files exported from the old platform contain multiple columns (e.g., number, status, time), you can upload them directly, but it is recommended to first clean them into a pure number column, because KK-DATA will re-detect and output the latest data.
If your raw data lacks certain fields (e.g., tgid, gender), don’t worry—KK-DATA will supplement them in the detection results. If your total raw numbers are insufficient, you can also use KK-DATA’s “Global Number Generation” feature (240+ countries/regions random generation, number range generation, custom CSV import) to expand your number pool.
Data Deduplication Tip
During migration, you can first import the list of numbers already screened by the old platform (numbers only) into KK-DATA’s “Data Deduplication Repository”. The system will automatically mark these numbers as “already detected”, avoiding duplicate charges in subsequent tasks.
Step 1: Register & Top Up Your KK-DATA Account
Go to the KK-DATA Application Console, no invitation code required. Register with your email. After logging in, navigate to the “Top Up” module:
- Deposit Method: USDT (TRC20) network, minimum approximately 50 USDT.
- Arrival Time: Usually within minutes; the system automatically updates the balance.
- Balance Inquiry: The available balance and frozen amount (estimated cost frozen while a task is in progress) are visible at the top of the console.
For first-time migration users, it is recommended to deposit an amount covering the estimated cost of at least 3 typical tasks (e.g., 5,000 Telegram valid detection + 2,000 activity detection + gender identification), to avoid running out of balance mid-process.
Deposit Suggestion
For your first deposit, consider 1.5 times the estimated cost, in case you need to add detection types or adjust task volume during migration.
Step 2: Import Numbers & Perform Deduplication
The core step of data migration is importing the number lists from the old platform into KK-DATA and using the deduplication repository to avoid redundant detection.
Upload Number File
Steps:
- Log in to the console → Click “Global Number Screening”.
- Click “New Task” → Select “Upload File”, supports CSV/TXT.
- After selecting the file, the system automatically parses the number column. If the file contains multiple columns, you can manually specify the column number containing the numbers.
- Select target platforms: Telegram, WhatsApp, iMessage, RCS, etc. (multiple selections allowed).
- Configure detection types: e.g., check “tg active”, “tg valid”, “tg activity (within 30 days)”, “gender identification”, “export tgid”.
- Click “Next” to enter the estimation interface.
Enable Deduplication Repository to Save Costs
When creating a new task, check “Enable Data Deduplication Repository”. The system will:
- Automatically compare numbers in the current task with the historical detected number library.
- Display the actual number of numbers to be detected after deduplication.
- Only charge for numbers not previously detected.
Important Notes:
- For the first migration, if you have a list of numbers already screened by the old platform (pure numbers), you can create a separate “Import Historical Detection” task, uploading only that list (check “deduplicate only, not detect”? Currently the API does not support a deduplicate-only mode, but you can use “Global Number Screening” to select the cheapest detection type (e.g., only active detection) and run it on that list; the system will then record them in the deduplication repository. This way, duplicate numbers in subsequent formal tasks will be skipped—it is recommended to contact official customer support first to confirm the best method, as the product may have been updated.)
- The deduplication repository works across tasks and supports long-term accumulation.
Step 3: Configure & Submit the Screening Task
After uploading numbers and enabling deduplication, fine-tune the configuration.
- Activity Window: Telegram activity can be set to 7 days, 15 days, 30 days, or custom days.
- Gender Identification: Based on avatar recognition; result fields are “male”, “female”, “unknown”.
- tgid/wsid Export: Check to include the platform’s user ID in the detection results (supported by the respective platform).
- Country/Region: Filter numbers by country, or generate/screen for specific countries.
Before submitting a task, the interface displays an estimated cost (sum of unit price for each selected detection type × actual number of numbers to detect). Confirm sufficient balance, then click Submit. The task will enter a queue, and upon completion, you can receive results via Telegram notification (requires binding a Telegram account in settings) or email.
Insufficient Balance Prevents Submission
The estimated cost must be lower than the current available balance. If the balance is insufficient, the Submit button will be disabled. It is recommended to top up to 1.5 times the estimated amount before submission, to accommodate potential additions of detection types during the task.
Step 4: Export Results & Continuous Usage Best Practices
Once a task is complete, you can download the results from the “Task Details” page in the console.
Export Format Selection & Field Descriptions
- CSV Format: Suitable for Excel processing. Each row includes columns such as number, platform, detection result, activity status, gender, tgid, wsid, etc.
- TXT Format: Contains only numbers, one per line, suitable for direct import into other systems.
- When exporting, you can also select to export only a specific subset (e.g., “valid” or “active” results).
Use the Generation Feature for Continuous Customer Acquisition
After migration, it is recommended to regularly use KK-DATA’s “Global Number Generation” feature to supplement new numbers:
- Random Generation: Select a country; the system generates random numbers based on real number ranges.
- Number Range Generation: Input a country and carrier prefix to batch generate consecutive numbers.
- Custom CSV Import: Upload your own number pool and combine it with the screening module to form a “generate → screen → export” pipeline.
Long-term usage recommendations:
- Regularly import “already detected history” into the deduplication repository to keep the deduplication baseline up to date.
- Store export results in categorized folders (by activity, gender, platform) for targeted marketing later.
- Set up Telegram notifications in the console to be promptly informed of task completion status.
Frequently Asked Questions
Q: Can data from 007data/thdata be directly imported into KK-DATA?
A: Usually yes. CSV/TXT files (number lists) exported from 007data/thdata can be directly uploaded in KK-DATA’s “Global Number Screening” module. If the raw file contains additional fields (e.g., detection results, tgid), we recommend cleaning it to a pure number column first, because KK-DATA will re-detect and output the latest data.
Q: Will my historical task data be lost after migration?
A: Data will not be automatically synchronized. You need to manually export the results file from the old platform; then, when creating a new task in the KK-DATA console, you can use the “Data Deduplication Repository” to import the historical number list (numbers only) to avoid duplicate charges. Detection result histories are not shared between the two platforms.
Q: Is KK-DATA’s billing more cost-effective than 007data/thdata’s?
A: It depends on usage frequency and detection types. KK-DATA charges per number (no subscription), suitable for users with fluctuating or low usage; 007data/thdata typically have subscription plans that may feel more valuable for high-frequency users. For specific unit prices, please refer to the official website/console real-time prices of each platform.
Q: Can I use both 007data/thdata and KK-DATA simultaneously?
A: Absolutely. Many users keep multiple platforms as backups or choose to use them for different detection needs. However, managing tasks and data across multiple accounts can be cumbersome; it is recommended to gradually migrate your main workflow to KK-DATA.
Q: Can KK-DATA’s Telegram screening identify gender?
A: Yes. KK-DATA supports gender identification via avatar (male/female/unknown) and can include this field in the exported results. This feature may require an additional fee or may not be supported on 007data/thdata; please refer to each platform’s actual functionality.
If you are considering migrating from 007data/thdata to KK-DATA, you can now log in to the KK-DATA Application Console to register and follow the steps in this article. For any issues, you can contact customer support via Telegram @kkdata_cc. For more details, please refer to the KK-DATA Usage Documentation and Billing Information.
Related Articles
Global Number Generation Capabilities: A Comprehensive Comparison of 007data, thdata, and KK-DATA's Number Generation + Filtering Pipeline
Need to generate global phone numbers in bulk for overseas marketing? This article provides a horizontal evaluation of global number generation capabilities on platforms like 007data and thdata, comparing them with KK-DATA's free generation + multi-platform filtering pipeline to help you choose the right tool and save costs. From country coverage, generation methods, billing models to data deduplication, get it all in one read.
Complete Tutorial: Migrating Phone Number Screening from thdata to KK-DATA – List Format, Task Creation, and Export Field Mapping Guide
Still using thdata? Step-by-step guide to migrate your Telegram/WhatsApp number screening data from thdata to KK-DATA. Covers list format conversion, console task creation, export field mapping, and a platform migration checklist. Ideal for overseas customer acquisition teams seeking a quick switch.
Migrating Number Screening from 007data to KK-DATA: Complete Operation Flow and Platform Migration Guide
Still using 007data for number screening? This article details the complete process of migrating from 007data to KK-DATA, covering list format conversion, console task creation, export field mapping, and best practices to help you seamlessly switch to a more flexible, pay-per-use screening platform. A must-read for overseas customer acquisition teams.