Migrating from 007 Data to KK-DATA Number Screening Platform: Complete Guide to List Format, Task Creation, and Export Fields

In overseas marketing and Telegram/WhatsApp community management, bulk number screening is essential for precise user targeting. In the past, many teams relied on 007 Data for number validation, but the platform has been shut down, leaving a large number of unverified phone lists and broken workflows. If you are facing the challenge of “migrating number screening from 007 Data,” this article provides a ready-to-implement guide: from number format conversion, console task configuration, to export field mapping—helping you seamlessly rebuild your screening pipeline on KK-DATA.

Why Migrate from 007 Data for Number Screening? — Platform Background and Necessity of Migration

Industry Impact After 007 Data Shutdown

007 Data was once the go-to screening tool for many overseas teams. After its shutdown, users not only lost historical screening results but more critically, could no longer submit new validation tasks. CSV/TXT lists (containing Telegram/WhatsApp numbers) piled up locally or in the cloud became “dead data.” Industry pain points are concentrated in three areas:

• No alternative: Finding a new platform on short notice requires relearning the operational logic.
• Incompatible list format: Export fields from 007 Data (e.g., “Phone Number”, “TGID”) are named differently from other platforms, potentially causing errors when uploaded directly.
• Non-transferable balance and historical data: Prepaid balances cannot be recovered, and previously screened TGIDs, activity levels, etc., need to be re-exported.

Thus, “migrating number screening from 007 Data” is no longer optional—it is a necessary step. Choosing a new platform that is comprehensive, multi-platform, and pay-as-you-go becomes a top priority.

Core Capabilities of KK-DATA as a Migration Candidate

KK-DATA is a number screening platform designed for overseas lead generation, covering Telegram, WhatsApp, iMessage, RCS, and more. Its core capabilities offer a strong alternative to 007 Data:

• Telegram Screening: Supports registration detection, active detection, activity (customizable windows like 7/15/30 days), gender identification (avatar-based), and TGID export.
• WhatsApp Screening: Valid number detection and WSID export.
• Global Number Generation: Random generation for 240+ countries/regions, number prefix generation, custom CSV import. Generation is free, screening is charged per number.
• Dedup Warehouse: Cross-task number deduplication to avoid wasting balance on duplicate checks.
• Pay-per-number: No subscription plans; pay only for what you use. Anonymous USDT recharge.

If you are looking for a replacement after migrating from 007 Data, KK-DATA’s feature matrix can seamlessly handle most of your validation needs.

Step 1: List Format Conversion — Transforming 007 Data Exports into KK-DATA Universal Format

Understanding 007 Data Common Export Formats

007 Data typically supports exporting in Excel (.xlsx), CSV, TXT, etc. Common export fields include:

• Phone Number
• Country Code
• Platform (e.g., TG/WA)
• TGID (Telegram ID)
• Active Days
• Gender

However, when preparing for batch upload, you only need to keep the pure number column. Extra fields may cause parsing errors in KK-DATA or increase file size. Steps:

1. Open the 007 Data exported file using Excel or Notepad++.
2. Delete all columns except the number column (including headers).
3. Ensure numbers are in full international format (e.g., +8613800138000). If the 007 export lacks ”+” or country code, add them manually.

KK-DATA Format Requirements for Number Lists

KK-DATA supports two mainstream formats:

• TXT: One number per line, no empty lines, no quotes.
• CSV: Single column of numbers, no header or first line as number (a column name like “phone” is optional but not required).

Example (TXT format):

+8613800138000
+85291234567
+14085551234

Checkpoints:

• Numbers must include international code (+86 or 86 both work, but using + is recommended to avoid ambiguity).
• No trailing spaces or invisible characters at the end of each line.
• File size should not exceed the single task limit (approximately 1 million lines). For larger lists, split into multiple files.

Step 2: Creating a Screening Task in KK-DATA Console — From Batch Upload to Detection Option Configuration

Selecting Platform and Detection Type

Log in to KK-DATA Console (https://app.kkdata.cc), click “Create Task” in the left navigation. First, select the target platform:

• Telegram: Detection options include:

  • Registration Check: Only checks if registered on Telegram.
  • Active Check: Registered and can receive messages.
  • Activity Check: Numbers that have logged in within the last 7/15/30 days (customizable).
  • Gender Identification: Identifies gender via avatar (returns m/f/unknown), requires “Activity Check” or “Active Check” as prerequisite.

• WhatsApp: Valid number detection (checks if registered on WhatsApp and usable).

• iMessage / RCS: For Apple devices and Android RCS protocol active number detection respectively.

Compared to 007 Data, KK-DATA offers more flexibility in Telegram activity windows (007 usually had a fixed number of days), and adds gender identification and WSID export, expanding data dimensions.

Uploading List and Estimating Fee

1. Click the “Upload Numbers” area; you can drag and drop a file or click to select.
2. The system automatically parses the file and counts the total number of entries (duplicates are marked but not automatically removed).
3. In the “Detection Configuration” on the right, check the required options. The system immediately shows the estimated fee (unit price × quantity). Actual deduction occurs from the balance after task completion.
4. Important: Ensure sufficient balance. If not, recharge USDT first (minimum ~50 USDT). All prices are based on real-time display in the console; see the official billing page for details.

Submitting Task and Checking Progress

Click “Submit” to queue the task. On the “Task Management” page, you can see statuses: In Progress, Completed, Failed. After completion, you can receive a notification via Telegram (requires binding a bot in settings). Export results will be available as a download link in the task details page.

Step 3: Export Field Mapping — Aligning KK-DATA Screening Results with 007 Data Fields

The biggest confusion after migration is: what do the familiar field names from 007 Data correspond to in KK-DATA? To reduce the learning curve, the table below shows common field mappings:

007 Data Export Field	KK-DATA Export Field	Description
Phone Number	phone	Original number, unchanged
TGID	tg_id	Telegram ID, only returned for Telegram detection
Active Days	last_active_day	Days since last active (e.g., 1 means active within 1 day)
Gender	gender	Gender: m (male), f (female), unknown
Country Code	country_code	Country code (e.g., 86)
Platform	type	Detection platform: tg / wa / imessage / rcs
WSID (WhatsApp User ID)	ws_id	Unique WhatsApp user identifier, requires WSID export option checked

Note: KK-DATA’s export column names may change with versions. Always refer to the column names shown in the console when exporting. It is recommended to check all columns on the first export, then rearrange in Excel.

KK-DATA vs 007 Data: Core Dimension Comparison for Platform Migration

The following comparison helps users objectively evaluate changes after migration:

Dimension	007 Data (Discontinued)	KK-DATA (Currently Available)
Billing Model	Previously pay-per-number	Pay-per-number, no subscription plans; see console for real-time pricing
Supported Platforms	Mostly Telegram, a little WhatsApp	Telegram, WhatsApp, iMessage, RCS
TGID/WSID Export	Only TGID	TGID + WSID, can export both simultaneously
Gender Identification	Not supported	Supported via avatar-based recognition
Data Deduplication	Manual deduplication required	Built-in dedup warehouse, automatic cross-task deduplication
Balance Top-up	No anonymous payment	Anonymous USDT TRC20 recharge
Task Limit	Unknown	Up to ~1 million numbers per single task

Best Practices and Common Pitfalls When Migrating from 007 Data

After assisting multiple teams with migration, here are common pitfalls and solutions:

1. Missing International Code: 007 Data may have only exported domestic number segments (e.g., 13800138000) without +86. Uploading directly leads to Telegram detection failures. Solution: Use a formula or script to prepend the country code uniformly (e.g., ="+86"&A2).
2. Duplicate Numbers Wasting Balance: 007 Data lists may contain previously screened numbers; resubmitting will cost extra. Solution: Use KK-DATA’s “Dedup Warehouse” feature. Import your list into the warehouse first, and the system automatically removes historical duplicates.
3. Gender Identification Requires Activity Check: KK-DATA’s gender identification relies on activity detection results. If you only check “Registration Check”, the gender field will not be returned. Solution: Check “Active Check” or “Activity Check” before also checking gender identification.
4. CSV File with BOM Header Causes Parsing Issues: UTF-8 CSV files sometimes have a BOM header (EF BB BF), which KK-DATA may not read correctly on the first line. Solution: Use Notepad++ to save as “UTF-8 without BOM” format.

Frequently Asked Questions

Q: 007 Data is no longer usable. Can my number list still be used?

A: Yes. As long as your number list is complete (with international codes) and saved in TXT or CSV format, you can upload it directly to the KK-DATA console for screening. It is recommended to first clean duplicates and use the Dedup Warehouse feature to avoid wasting balance on repeated checks.

Q: Are KK-DATA screening results as accurate as 007 Data?

A: Both use different detection protocols and technical implementations, so accuracy cannot be directly compared. KK-DATA supports Telegram official registration/activity detection, WhatsApp valid number validation, and iMessage/RCS checks. We suggest testing with a small sample (100 numbers) on KK-DATA and comparing the results with any sample results you retained from 007 Data before bulk usage.

Q: Do I need to relearn operations when migrating from 007 Data to KK-DATA?

A: The overall process is similar: upload list → select detection options → submit task → export results. KK-DATA’s console is designed for batch workflows, supporting up to 1 million numbers per task, TGID/WSID export, Dedup Warehouse, and other advanced features. We recommend reading the official documentation (https://docs.kkdata.cc) for a quick start.

Q: Which platforms does KK-DATA support for screening? Does it cover the same as 007 Data?

A: KK-DATA currently supports Telegram, WhatsApp, iMessage, RCS, and other platform checks. Empty number detection and carrier identification features depend on what is available in the console. 007 Data mainly focused on Telegram and a small amount of WhatsApp. KK-DATA has broader platform coverage, especially adding iMessage and RCS, which is suitable for Apple ecosystem and overseas Android marketing scenarios.

Q: After migration, can I retain my original detection results from 007 Data?

A: The 007 Data platform is closed, so historical results cannot be exported via API. If you have locally saved CSV/TXT files containing TGID, active days, etc., you can directly import them as reference data into your business system. However, when checking new numbers on KK-DATA, it is recommended to resubmit the original list to obtain the latest status (e.g., numbers may have been deactivated).

---

By following the steps above, you should be able to successfully complete the migration from 007 Data for number screening. If you encounter specific issues during operation, check the KK-DATA Usage Documentation or contact official support (@kkdata_cc) for assistance. Log in to the Console now and start creating your first task.