Complete Guide to Number Screening Platform Migration: How to Seamlessly Switch and Retain Your Lead Data

Number screening platform migration refers to the process of completely and accurately transferring your existing phone number lists, screening results, and valid data from the old platform to the new one. This is not a simple file copy, but a process involving data format conversion, field mapping, duplicate detection, and task verification.

Why Should You Migrate Your Number Screening Platform?

The reasons teams consider migration are usually practical: the old platform lacks features (e.g., it cannot detect activity status or gender), price adjustments have increased costs, data security is no longer guaranteed, or the platform itself is discontinuing service. More commonly, teams want to find a platform that supports multi-platform screening (Telegram, WhatsApp, iMessage, etc.) and offers more flexible billing. Whatever the reason, a successful platform migration can directly extend your lead generation capabilities and prevent data asset gaps.

---

3 Preparation Checklist Items You Must Do Before Migration

Before starting, verify each item against the following checklist. Missing any one can affect migration quality.

Checklist 1: Export the Number List and Results from the Original Platform

Export all data from the old platform, typically in CSV or TXT format. Ensure the exported file includes the following fields:

• Original number (including country code, e.g., +8613800138000)
• Screening result (e.g., “Valid”, “Invalid”, “Active”, “Inactive”)
• Additional information (TGID, WSID, gender, last active date, etc.)
• Export timestamp (to determine data freshness)

Note: If the old platform only provides a binary “Valid/Invalid” result, while the new platform supports more granular detection (e.g., active days, gender), it is recommended to directly use the new platform to detect numbers that have not been tested, rather than reusing old data.

Checklist 2: Understand the Field Mapping Rules of the Target Platform

Field mapping refers to mapping each column of data exported from the old platform to the field names and formats recognized by the new platform. For example:

Old Platform Field	New Platform Field (KK-DATA Example)	Description
Number	phone	Must include country code, e.g., 8613800138000
Status	Detection Result	Mapped to standard values such as “Registered / Valid / Not Registered”
Last Login Time	Active Days	Converted to days from today (e.g., 7 means active within 7 days)
TG Username	tgid	The TGID exported from the old platform can be directly mapped

If the old platform fields cannot be directly mapped (e.g., old platform custom tags), it is recommended to discard that field to avoid recognition errors after upload.

Checklist 3: Back Up Data and Test in Small Batches

It is strongly recommended to first extract 50–100 numbers from the old list as a test set and upload them to the new platform for detection. The goal is to verify:

• Whether field mapping is accurate
• Whether the number format is correctly parsed
• Whether the detection results are consistent with the old platform (or within a reasonable range)
• Whether the deduction logic works as expected

Do not upload tens of thousands of numbers for testing at once, as the cost of fixing problems after they are discovered will be extremely high.

---

How to Perform Number Format Conversion and Field Mapping?

Common Field Correspondence Examples

Standard field mapping table (can be copied to Excel as a template):

Old System Field	New Platform Field	Format Requirement	Notes
Phone Number	phone	Numeric format, no + or spaces	Excel formula: =SUBSTITUTE(A1,"+","")
Status	Detection Result	Leave blank if no mapping	Old results cannot be directly reused on new platform
Last Active	Active Days	Number (e.g., 7 means within 7 days)	If old platform data is more than 30 days old, recommend re-testing
Gender	gender	male / female / unknown	Leave blank if old platform has no such data
TG Username	tgid	Pure numeric ID	Ensure no usernames (e.g., @username) are mixed in

Pitfalls in Format Conversion and Solutions

The following issues are common in practice. Prepare in advance:

1. Delimiter inconsistency: Old platform uses comma (,), new platform requires Tab (\t). You can replace in a text editor or use Excel’s “Text to Columns” feature to adjust.
2. Encoding issues: Old file is GBK encoded, new platform requires UTF-8. It is recommended to use Notepad++ or VS Code to uniformly convert to UTF-8 without BOM.
3. Blank lines and spaces: Spaces before or after a number can cause parsing failure. Use Excel’s TRIM() function to clean.
4. Country code format inconsistency: Some have + (e.g., +86138), some have 00 (e.g., 0086138), some are pure numbers (e.g., 86138). It is recommended to uniformly convert to pure numeric format (e.g., 8613800138000), keeping the country code (86) and the number.

---

How to Avoid Duplicate Detection and Balance Waste During Migration?

Duplicate detection is the most common waste during migration. Numbers already detected on the old platform will be charged again if resubmitted on the new platform. Solutions:

1. Merge old and new lists and deduplicate: Merge all numbers from the old platform with new numbers that need to be added, and remove completely duplicate rows. If numbers have timestamps, it is recommended to keep only the most recent record.
2. Use the new platform’s deduplication feature: For example, KK-DATA’s Data Dedup Warehouse automatically filters numbers that have been previously detected on the platform (cross-task, cross-user) when uploading files, and only charges for new numbers. Enabling this feature prevents duplicate charges even if old platform data is mixed in.
3. Clean invalid data: Remove clearly irregular rows (e.g., blank lines, pure letter rows, numbers with incorrect digit lengths) to reduce invalid uploads.

---

Correct Sequence of Batch Testing and Task Execution

It is recommended to follow a “small batch → medium scale → full volume” three-step approach:

Step 1: Small Batch Test (50–100 numbers)

• Check if field mapping is accurate
• Confirm whether detection results (e.g., activity rate, gender ratio) are within expected range
• Verify estimated cost vs. actual deduction

Step 2: Medium Scale Verification (1000–5000 numbers)

• Observe task execution speed
• Check if exported TGID/WSID comply with format
• Sample compare results between old and new platforms

Step 3: Full Volume Migration (whole list)

• Ensure sufficient balance
• Configure task notifications (e.g., Telegram notification), check immediately after completion
• Do not delete the original old platform backup before exporting results

---

How to Verify Data Consistency After Migration?

Completion of migration does not mean the end; consistency verification must be performed:

1. Sample compare activity rate: Randomly extract 100 numbers from the new platform’s detection results and compare their “Valid/Active” flag with the old platform results. A deviation of ±5% is acceptable.
2. Check TGID/WSID format: Exported TGID should be purely numeric, WSID should be an identifier (e.g., +86138... format), ensure no extraneous characters are mixed in.
3. Verify dedup effect: Check the dedup report generated by the new platform to confirm duplicate numbers were not charged.
4. Gender ratio: If the old platform exported gender data, sample compare accuracy.

If significant deviations are found (e.g., activity rate drops from 60% to 20%), it indicates issues in field mapping or number cleaning. Roll back to the test set and re-adjust.

---

Long-Term Operation Suggestion: Establish a Reusable Migration SOP

Number screening platform migration should not be a one-time project. It is recommended to document the following assets to form a reusable standard operating procedure:

• Field mapping table (Excel/Google Sheets shared document)
• Data cleaning script (Python or Excel formulas)
• Test records (activity rate, deduction amount, etc. from each test)
• Migration timeline screenshots (for auditing)

The benefit: even if you change platforms again in the future, or a new team member takes over, they can quickly complete the migration according to the SOP without repeated trial and error.

---

Frequently Asked Questions

Q: The numbers exported from the old platform have the “+86” format. Does the new platform support this?
A: Most platforms support international format and do not require manual removal of the ”+”. It is recommended to directly upload numbers with country code; the platform will automatically recognize them. If the platform requires pure numbers, use the Excel formula =SUBSTITUTE(A1,"+","").

Q: Will numbers already detected on the old platform be charged again if detected on the new platform?
A: If the new platform provides a dedup warehouse (e.g., KK-DATA’s Data Dedup Warehouse), the system will automatically filter out previously detected numbers during upload, avoiding duplicate charges. It is recommended to clean redundant records from the old platform’s exported results before migration.

Q: After migration, some numbers cannot be detected or show “Invalid”. What are the possible reasons?
A: Possible reasons: incorrect number format (e.g., missing country code), wrong country code (e.g., missing area code), the target platform does not support that number type (e.g., some virtual operator numbers). It is recommended to check the original data and first submit a small batch for testing.

Q: Do I need to deposit a large balance all at once for the migration process?
A: No. With pay-per-number billing (like KK-DATA’s model), it is recommended to first deposit the minimum amount (e.g., 50 USDT), complete the test, and then gradually top up. Avoid depositing a large amount upfront and then having funds tied up due to migration interruption or plan adjustments.

Q: After migration, I found that field mapping errors caused a large number of detection results to be useless. What should I do?
A: Before the official migration, be sure to perform a small batch test. If a large-scale error has already occurred, check if the mapping relationship is correct, re-upload the correctly mapped list, and delete (or ignore) the incorrectly detected data from the new platform. It is recommended to keep the old platform data backup for rollback.

---

Start Efficient Number Screening Now

Whether due to insufficient features, price changes, or seeking more flexible billing, number screening platform migration is a key step to improving lead generation efficiency. KK-DATA provides one-stop number generation, multi-platform screening, data dedup warehouse, and other features to help you transition smoothly and continuously acquire high-quality target users.

👉 Log in to the console to start screening
Two-way contact customer service: https://t.me/kkdata_robot
Detailed documentation: https://docs.kkdata.cc/