Number Screening System Migration Guide: How to Smoothly Switch Platforms While Preserving Field Mapping and Lists

In batch verification scenarios, many teams encounter the same problem when switching to a new number screening platform: the old platform’s number lists and detection results cannot be directly transferred, leading to redundant manual effort, loss of historical data, and even critical field misalignment. This Number Screening System Migration Guide provides a reusable four-step plan—from exporting lists, field mapping, test batches, to formal switchover—to help you safely transition to a new platform (e.g., KK-DATA) and avoid common pitfalls.

---

What is Number Screening System Migration and Why Do You Need a Migration Guide?

Number screening system migration refers to the process of switching from one number screening platform (old platform) to another (new platform, e.g., KK-DATA). It sounds like simply “changing tools,” but in practice, three major pain points often arise:

• Field mismatch: The old platform’s “registered” may be “registration check” on the new platform; the old platform’s “active” window may differ from the new platform’s default.
• Historical data loss: Numbers already screened on the old platform are not marked, leading to duplicate charges when re-screened on the new platform.
• Wasted balance: Remaining balance on the old platform cannot be transferred, and the new platform requires a new top-up.

Having a structured migration guide allows you to clarify data inventories, define field mapping rules, and verify consistency with small batches before switching, significantly reducing trial-and-error costs. This guide focuses on Telegram and WhatsApp number screening scenarios, using KK-DATA as the example new platform (which offers deduplication repositories, custom activity windows, and pay-per-number billing, ideal for migration scenarios).

---

What Data Inventory Should You Prepare Before Migration?

Before starting any operation, organize the following four types of materials. It is recommended to store all files in an encrypted folder and keep a version backup.

Export Original Number Lists and Deduplication Files

• Pending screening lists: CSV/TXT files you originally uploaded on the old platform (containing the column of numbers to be screened).
• Existing screening results: All result files generated by the old platform (usually containing columns such as “number”, “status”, “activity”, “gender”, “tgid/wsid”, etc.).
• Historical balance screenshots: Screenshots of recharge records and remaining balance from the old platform (used for calculating economic compensation during migration; if a refund is not possible, try to consume the balance).

Organize Field Definitions from the Old Platform (e.g., “Valid”, “Active”, “tgid”)

Field mapping is the key to migration success. You need to clarify the business meaning of each field on the old platform. For example:

• “Registered” → Whether the number is registered on Telegram?
• “Valid” → Beyond registration, are there additional conditions (e.g., active in the last 30 days)?
• “Active” → Has the number sent a message or been online in recent days?
• “Gender” → Is it identified through AI analysis of the avatar?
• Were tgid (Telegram user ID) or wsid (WhatsApp user ID) exported?

Tip: If the field names in the old platform’s result files are ambiguous, first use 100 known numbers to run a detection on the old platform and observe the meaning of the returned values.

---

How to Perform Field Mapping? How to Correspond New and Old Platform Screening Results?

Below, using Telegram and WhatsApp as examples, we show common field mappings between old and new platforms. Specific detection type names should be based on the new platform’s console; here, we use KK-DATA’s naming conventions.

Telegram Field Mapping Example

Old Platform Field (Example)	New Platform Field (KK-DATA)	Notes
Registration status	tg开通 (registration check)	Checks whether the number is registered on Telegram
Valid status	tg有效	Usually means registered and can receive messages
Last login days	tg活跃 (7/15/30 days)	Must align the window duration
Gender (avatar recognition)	telegram 性别数据	Both based on AI avatar analysis
tgid (user ID)	tgid export	Note: old platform may require separate export checkbox

“Active window days” is a common source of errors. If the old platform uses “active within 30 days” and the new platform defaults to “active within 7 days”, the number of active users after migration will significantly drop. KK-DATA supports selecting 7/15/30 custom windows in tasks; be sure to align manually.

WhatsApp Field Mapping Example

Old Platform Field (Example)	New Platform Field (KK-DATA)	Notes
Whether registered on WhatsApp	WhatsApp 有效号码检测	Checks if the number is registered on WhatsApp
wsid (user ID)	wsid export	Exports WhatsApp user ID
Last online time	Not provided	If the old platform has this field, assess the impact after migration

Note: Different platforms have different detection depths. For example, some old platforms may provide “precise last online time”, while the new platform only returns “valid/invalid”. In such cases, you need to determine whether you really need that field, or if you can indirectly substitute it with activity data.

---

Batch Testing: How to Verify the Migration Plan with a Small Amount of Data?

Do not migrate the entire list at once. First, run a small batch test to validate the full workflow and confirm field mapping is correct before proceeding to full-scale operation.

Test Steps

1. Select test samples: Extract 2,000 to 5,000 numbers from the historical list. It is recommended to include three categories:
   • Known valid and active numbers (positive controls)
   • Known invalid/unregistered numbers (negative controls)
   • Numbers with known gender (for verifying gender recognition)
2. Create a task on the new platform:
   • If the new platform (e.g., KK-DATA) offers a “data deduplication repository”, first import the test numbers into the repository to avoid duplicate charges later.
   • Select the corresponding detection types (tg开通, tg有效, tg活跃, etc.) and set the same activity window as the old platform.
   • Submit the task and wait for completion.
3. Compare results:
   • Export the new platform results and compare them row by row with the old platform’s detection results.
   • Key focus: total valid numbers deviation ≤ 5%; active ratio deviation ≤ 5%; gender distribution roughly consistent.

If the deviation exceeds 5%, stop and troubleshoot (refer to Section 5: Field Mapping Errors). Only proceed with full migration after confirmation.

---

Formal Migration: Correct Order for List Import and Task Execution

After the small batch test passes, perform the full migration in the following order:

1. Register/login to the new platform and top up balance: Visit https://app.kkdata.cc/ to create an account. Recharge balance via USDT (TRC20) (pay-per-number, no subscription plans). It is recommended to top up an amount covering the estimated number of detections (calculate roughly based on the historical quantity on the old platform times the platform’s unit price; see official billing page).
2. Create a “data deduplication repository” and import old data: In the new platform’s dashboard, go to “Data Deduplication Repository” and upload all numbers that were previously screened on the old platform (only the number column, no results needed). This prevents duplicate charges for already processed numbers.
3. Upload the list to be screened: Upload the numbers that have not been screened on the old platform, or the full list that needs to be re-screened (CSV/TXT format, ensure numbers include international dial codes).
4. Select detection types: Check the required screening items by platform (Telegram / WhatsApp / iMessage, etc.). Pay special attention to “active window days” to match the old platform.
5. Review estimated cost and submit: The new platform shows an estimated cost before submission. Confirm the amount and submit the task.
6. Wait or receive notification: After the task completes, KK-DATA supports sending completion notifications via Telegram bot. You can also view results in the console.
7. Export results: Download screening results in CSV or TXT format. If you need tgid/wsid, ensure you select the format that includes these fields.

---

How to Check Data Consistency After Migration?

Immediately after full migration is complete, perform a data consistency check. Below is a checklist:

• Compare key metrics: For the same set of numbers, the deviation in “total valid”, “active ratio”, “gender distribution” between old and new platforms should be less than 5%.
• Random sampling: Extract 100 numbers from each of the old and new results, and manually verify them on the real Telegram/WhatsApp client or via third-party API (e.g., search username, send temporary message). If the old platform already has verification records, compare directly.
• Field format consistency: Ensure that exported tgid (numerical) and wsid (may contain special characters) are not truncated or garbled in the CSV. If the old platform’s tgid is a string and the new platform is numeric, a type conversion may be needed.

If a deviation of more than 5% is found, fall back to the testing steps for further investigation (see next section on common mapping errors).

---

Common Field Mapping Errors During Migration and Solutions

Mapping “Active” to “Registered”

• Phenomenon: The number of “valid” on the new platform is much larger than on the old platform.
• Cause: The old platform’s “valid” might have included an activity check (i.e., only counting recently active users), while the new platform’s “tg开通” only checks registration, not activity.
• Solution: Map the old platform’s “valid” to the new platform’s “tg有效” or “tg活跃” (with the same window), not to “tg开通”.

Ignoring Gender Recognition Field

• Phenomenon: The gender column on the new platform is blank or the results differ significantly.
• Cause: The old platform had gender recognition enabled by default, while the new platform requires manually checking the “telegram gender data” detection item.
• Solution: When creating the task, explicitly check the gender recognition option (may incur additional charges).

Forgetting to Export tgid

• Phenomenon: The new platform results only contain phone numbers, no tgid column.
• Cause: The new platform requires selecting “include tgid” in the export settings.
• Solution: Re-export the results with the format that includes tgid (KK-DATA supports custom export fields).

Inconsistent Active Window Days

• Phenomenon: The “active” ratio differs significantly between old and new platforms (e.g., 20% vs 5%).
• Cause: The old platform used “active within 30 days”, while the new platform defaults to “active within 7 days”.
• Solution: In the new platform task, select the same window days as the old platform (7/15/30 days), or unify according to business needs.

---

How Long Does It Take to Stabilize After Migrating to a New Screening System?

A recommended adaptation period is 1–2 weeks. During this time:

• Run two systems in parallel: Keep the old platform’s balance and do not deactivate it immediately. After running 3–5 complete tasks on the new platform (covering different platforms and detection types), compare result consistency.
• Closely monitor backend notifications: The new platform (e.g., KK-DATA) provides Telegram task completion notifications. Pay attention and contact support immediately if anything abnormal is found.
• Gradually shut down the old platform: Only after confirming no deviation, consume the remaining balance on the old platform or request a refund, then officially say goodbye to the old platform.

---

Frequently Asked Questions

Q: Can the balance from the old screening platform be refunded after migrating to a new one?
A: Usually, balances from old platforms cannot be transferred across platforms. It is recommended to use up the old platform’s balance as much as possible before migration, or contact the old platform’s customer service for refund policies. The new platform (e.g., KK-DATA) supports USDT pay-per-number billing, no subscription plans, so you pay for what you use and avoid wasting balance.

Q: Can I directly upload the old platform’s number list to the new platform?
A: Yes. Most screening platforms accept CSV/TXT format number files. Just ensure the number column format is correct (e.g., includes international dial codes, no spaces). It is recommended to first upload a small list to test format compatibility.

Q: After field mapping, will the definition of “active” be the same on both platforms?
A: Not necessarily. Different platforms may define the “active” judgment window differently (e.g., 7 days, 15 days, 30 days). During migration, clarify the new platform’s active window options and align with the old platform. KK-DATA supports custom 7/15/30 day activity detection for manual correspondence.

Q: If data deviation is found after migration, how to quickly locate the problem?
A: Keep the complete export results of the old platform’s most recent task. Use the same number list to re-screen on the new platform and compare the two result files with Excel. Focus on the “valid” and “active” columns. If deviation exceeds 5%, first check field mapping and detection type selection.

Q: There are many duplicate numbers in the list. How to avoid duplicate charges after migration?
A: Use the new platform’s data deduplication repository. Before submitting a new task, import all historical numbers from the old platform into the repository. The new platform will automatically skip already processed numbers during detection. KK-DATA has a built-in cross-task deduplication repository to save balance effectively (see official billing page for details).

---

The above is the complete Number Screening System Migration Guide. Regardless of which platform you are migrating from, it is recommended to follow the workflow: “Backup inventory → Field mapping → Small batch testing → Full migration → Consistency check”. On the new platform, KK-DATA offers a deduplication repository, custom activity windows, and pay-per-number billing to reduce migration costs and trial-and-error risks. Log in to the console now to start your migration test:

👉 Log in to console to start screening
Contact us on Telegram: https://t.me/kkdata_robot
Documentation: https://docs.kkdata.cc/