Migrating from 007data to KK-DATA: Complete Operation Process and Platform Migration Guide

If you have been using 007data for number screening for a long time, you may have felt the inflexibility of the subscription model or encountered functional bottlenecks in scenarios like Telegram activity detection or gender identification. This article will detail the complete migration process from 007data to KK-DATA—from list format conversion to console task creation to result field mapping—helping you smoothly switch to a more flexible, pay-per-use screening platform. The migration cost is low—list formats are highly compatible, and after migration you can leverage unique features to boost efficiency.

Why Migrate from 007data to KK-DATA?

007data has some foundation in basic number verification, but if you need more detailed user profiles, greater export freedom, or want to get rid of fixed subscription fees, KK-DATA offers several key differentiators:

Aspect	007data (based on public info)	KK-DATA
Detection types	Mainly registered/invalid	Supports registered, valid, active (specified window), gender identification, tgid/wsid export
Billing model	Subscription/package	No subscription, pay per check, pay only for what you use
Payment method	Conventional payment	USDT (TRC20) anonymous recharge
Data deduplication	Not publicly supported	Data deduplication warehouse, automatic deduplication across tasks
Export freedom	Limited fields	Supports CSV, TXT multi-format export with rich fields
Task notification	Not publicly supported	Supports Telegram notification upon completion

Core drivers for migration: Supports Telegram activity detection (check if online in last 7/15/30 days) and AI-based gender identification from avatars; no subscription plans, pay per check means you only pay for actual detections; USDT anonymous recharge gives more flexibility in fund management; number generation module is free, forming a “generate → screen → export” pipeline.

Key point: Migration cost is low. Lists exported from 007data (CSV/TXT) are highly compatible with KK-DATA—only simple format cleaning is needed for reuse. After migration, you not only retain historical data assets but can also use the deduplication warehouse to avoid wasting balance on duplicate detections.

Pre-Migration Preparation: Export 007data Lists and Review Fields

Before starting the migration, complete these two steps:

1. Export 007data raw data: Log in to the 007data backend and export by platform (e.g., Telegram, WhatsApp) and batch (e.g., 2024 Q1 list). It is recommended to back up complete data, including numbers, status, tgid, wsid, and any notes or tags you added yourself.
2. Review fields: The key fields are number (must be in international format, e.g., +8613901234567), whether tgid/wsid is included, and whether to preserve notes. If number formats are inconsistent, additional cleaning will be needed later.

Check Common Formats Exported by 007data

007data typically supports CSV and TXT export. Common column name examples:

• Number: May appear as “手机号”, “Number”, “Phone”
• Status: May appear as “状态”, “Status”, values like “有效” (valid), “无效” (invalid), “未注册” (unregistered)
• Active: May appear as “最近在线” (last online), “活跃天数” (active days), “Last Online”
• TG_ID: May appear as “TG ID”, “tg_id” (if 007data supports export)

You need to confirm which columns are essential after migration. Usually, the number is the only required column; if you need to keep tgid or active status, you can extract them separately during cleaning.

Confirm KK-DATA’s Supported Input Format

KK-DATA console (https://app.kkdata.cc/) directly supports CSV and TXT file upload, as well as manual pasting of numbers. Number format requirements:

• Must start with ”+” in international format, e.g., +8613901234567
• One number per line, no header required
• Supports blank lines and pure numeric format (but it is recommended to unify to international format)

This means you don’t need complex conversion. Simply clean empty lines, garbled characters (e.g., special characters, spaces, parentheses), and then remove extra columns (keep only the number column).

List Format Conversion: 007data → KK-DATA Standard List

Step-by-step:

1. Open the CSV exported from 007data (using Excel or Notepad)
2. Keep only the number column: Delete extra columns like status, active, etc. If you need to keep notes, you can save them in a separate column—they won’t affect the screening judgment.
3. Clean number format:
   • Remove spaces: In Excel, use =TRIM(A1) or Find & Replace (Ctrl+H) → replace space with nothing
   • Add ”+”: If numbers are purely numeric (e.g., 8613901234567), use Excel formula ="+"&A1
   • Remove parentheses and hyphens: Find ( and ), -, replace with nothing
4. Save as CSV (UTF-8 encoding) or TXT

Batch Conversion Methods

• Excel formula: Assume column A contains original numbers; enter ="+"&A1 in column B, then drag down. If original numbers have inconsistent formats (e.g., mixing +86 and 86), first use formula =IF(LEFT(A1,1)="+",A1,"+"&A1) to handle.
• Notepad++ regex: Open the TXT file, search for [^0-9\n] (non-digit and non-newline), replace with empty; then manually add ”+” at the beginning of each line (or use a macro).
• Validation: After each conversion, randomly sample 10 numbers and manually check if the format becomes +8613901234567. If any number contains a country code (e.g., 86 but missing ”+”), be sure to add it.

Large File Splitting Suggestion

007data lists can be large. KK-DATA supports up to about 1 million numbers per task. If your file exceeds 1 million lines, consider the following approach:

• Use Excel or command-line tools (e.g., split command) to split into batches of 1 million lines each
• Upload separately to the console and create multiple tasks
• Use KK-DATA’s data deduplication warehouse to first import all batches, then submit screening tasks—it will automatically exclude duplicates

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

Log in to https://app.kkdata.cc/ and follow the steps below.

Telegram Screening Example (Detect Registered/Valid/Active/Gender)

1. Click “Screening Tasks” in the left menu → “Create Task”
2. Select Platform: Choose “Telegram”
3. Select Detection Types:
   • tg registered: Check if number is registered on Telegram
   • tg valid: Check if account is in valid state (can send messages)
   • tg active: Specify active window (7/15/30 days) to check when user was last online
   • telegram gender: AI-based gender identification from avatar
   • tgid export: Output the Telegram user ID for each number
4. Upload List: Click “Choose File” and select the cleaned CSV or TXT
5. Set Parameters: For activity detection, enter the window days; if tgid is needed, check the export option
6. Estimate Cost: System automatically calculates based on list size and detection types (displayed as “Estimated Detection Cost”). Check if balance is sufficient.
7. Confirm Submission: Click “Submit Task”

WhatsApp Screening Example (Detect Valid/wsid Export)

1. Create task → Select “WhatsApp”
2. Detection type choose “WhatsApp valid”, or also check “wsid export”
3. Upload list (same format as Telegram)
4. Confirm cost and submit

After submission, the system will start processing. Upon completion, you can download the results (CSV or TXT) from the “Task Details” page. If Telegram notification is enabled, you’ll receive a completion alert.

Export Field Mapping: 007data vs KK-DATA Result Field Correspondence

After migration, you need to understand how KK-DATA output fields correspond to those from 007data. The table below helps you quickly adapt to the new system:

007data Example Field	KK-DATA Corresponding Field	Description
Number	phone	International format, exportable
Status (registered)	tg_registered	true (registered)/false (unregistered)
Active (last online)	tg_last_active_days	Number, active window selectable 7/15/30 days
TG ID	tg_id	Direct export, no extra conversion needed
Avatar gender	gender	male/female/unknown, based on AI avatar recognition
WhatsApp valid	wa_valid	true/false
WhatsApp ID	wa_id	Only valid numbers have value

Key differences: KK-DATA additionally supports “gender identification (avatar)”, “tgid export”, “wsid export”. These are generally unavailable in 007data or require extra tools. If you need more detailed user profiles, migration will significantly improve efficiency.

Best Practices After Migration: Leverage KK-DATA’s Unique Features

Migration is not just about switching platforms—it’s an efficiency upgrade. We recommend you start using these features immediately:

1. Global Number Generation (Free): If you need to expand into new markets, first use KK-DATA’s global number generation module (covering 240+ countries/regions). Generating numbers is free. After generation, directly import them into a screening task, forming a “generate → screen → export” loop.
2. Data Deduplication Warehouse: This is a core feature. After migration, first import all historically detected numbers from 007data into the deduplication warehouse. In subsequent screening tasks, check “Enable Deduplication”, and the system will automatically skip already-detected numbers, avoiding duplicate charges. To operate: go to the console’s “Data Warehouse” module, upload the number list, and set the deduplication scope.
3. Task Notification (Telegram Alert): Bind your Telegram account (@kkdata_cc) in the console to receive automatic notifications when tasks complete. No need to manually refresh the page—ideal for batch task scenarios.
4. Multi-Format Export: Results support CSV and TXT. If you need to import tgid or wsid into other tools, simply select “Export tgid column” or “Export wsid column”—no secondary parsing needed.

Scenario Example: You have a historical number library of 1 million numbers that were tested on 007data but need updated activity status. After migrating to KK-DATA:

• Import old numbers into the deduplication warehouse (marked as “already detected”)
• Create a new Telegram activity detection task, check “Exclude numbers in deduplication warehouse”
• The system will only test new or undetected numbers, saving about 80% in costs

Frequently Asked Questions

Q: Can the CSV exported from 007data be directly imported into KK-DATA?

A: In most cases yes, but it’s recommended to clean the column names, keep only the number column, and unify the number format to international format (+country code + number). KK-DATA supports CSV and TXT. If the original file contains notes or tags, you can keep them via a notes column—they won’t affect screening. When cleaning, remember to remove empty lines and garbled characters.

Q: What are the billing differences between KK-DATA and 007data?

A: 007data generally uses a subscription or fixed monthly package model—you pay a fixed fee but may not fully use the quota. KK-DATA uses a no-subscription, per-rate deduction model: you recharge, and each detection deducts the corresponding fee. You pay only for what you use, giving more flexibility. For specific prices, please refer to the KK-DATA console real-time pricing (https://kkdata.cc/billing/).

Q: Will the original tgid data be lost after migration?

A: No. You can use the tgid exported from 007data as input and re-run detection on KK-DATA to update activity or gender data; alternatively, you can directly use KK-DATA’s “tgid export” function to reacquire them. KK-DATA supports tgid as a screening input field, so your data assets remain usable after migration.

Q: Can 007data verify Telegram activity? What about KK-DATA?

A: According to public information, 007data mainly checks whether numbers are registered or invalid. KK-DATA additionally supports “active” detection, allowing you to specify 7/15/30-day active windows; it also supports gender identification based on avatars, and direct tgid/wsid export. If you need more detailed user profiles (e.g., whether the user has been online recently), migrating to KK-DATA would be more suitable.

Q: What is the data deduplication warehouse? Does 007data have a similar feature?

A: The data deduplication warehouse is a distinctive feature of KK-DATA, supporting cross-task number deduplication to avoid wasting balance on duplicate detections. 007data has not publicly disclosed such a feature. After migration, we recommend first importing all historically detected numbers into the deduplication warehouse, then new tasks will automatically exclude already-detected numbers. This can save significant costs in batch operations.

---

Action Recommendations:

• Immediately log in to the KK-DATA Console to start your first screening task
• Check the Detailed Operation Documentation for advanced fields and batch import guides
• For migration questions, contact the official Telegram support @kkdata_cc for one-on-one assistance