Migrating from Magic Cube Data to KK-DATA: Complete Guide to List Conversion, Task Configuration, and Export

If you previously used the Magic Cube Data platform for batch number screening and are now considering migrating to another tool due to stalled feature updates, inflexible billing models, or limited export flexibility, this guide is for you. We’ll walk you through the smooth migration of your existing lists, formats, and console tasks from Magic Cube Data to KK-DATA, covering number format conversion, field mapping, batch task creation, and result export. This will help your overseas team quickly switch platforms, avoid data waste, and eliminate redundant work.

---

Why Migrate Number Screening from Magic Cube Data? – Core Considerations for Platform Switching

Any tool switch should be based on a practical evaluation of features, cost, and efficiency. Magic Cube Data, as an early entrant into the number screening tool market, helped many overseas teams get started. However, as business scales, some users encounter the following bottlenecks:

• Slow feature updates: Detection rules for social platforms (e.g., Telegram, WhatsApp) change frequently. Older platforms may not adapt in time, leading to decreased detection accuracy.
• Insufficient granularity in activity screening: Magic Cube Data’s activity detection typically offers only fixed tiers (e.g., “active within 7 days” or “active within 30 days”), while certain marketing scenarios require more flexible custom windows (e.g., 15 days, 20 days).
• Limited multi-platform support: Besides Telegram and WhatsApp, Magic Cube Data may lack coverage for emerging screening types like iMessage, RCS, and empty number/carrier detection.
• Inflexible billing models: Subscription or package plans mean you pay a fixed fee even when business volume is low in a given month. Pay-as-you-go models offer more budget control.
• Weak data deduplication: Lack of global deduplication across tasks means repeatedly detecting the same numbers wastes significant costs.
• Limited export formats: Only basic fields can be exported, lacking deep data like tgid and wsid, and custom columns cannot be selected.

KK-DATA, as a next-generation customer acquisition data screening platform, has made targeted optimizations in these areas. Below is an objective comparison of the differences between the two (note: comparison based on public information; actual features depend on each platform’s current version).

Comparison Dimension	Magic Cube Data (Typical Features)	KK-DATA
Billing Model	Subscription or package plans	No subscription, pay per record, usage-based
Activity Detection	Fixed tiers (e.g., 7/30 days)	Custom windows (7/15/30 days, etc.)
Multi-platform Coverage	Primarily TG/WA	Additional support for iMessage, RCS, empty number/carrier detection
Data Deduplication	Weak cross-task deduplication	Built-in data deduplication warehouse, auto deduplication across tasks
Export Depth	Basic fields	Supports tgid and wsid export
Recharge Method	Fiat + bank card	USDT (TRC20) anonymous recharge
Format Compatibility	Proprietary format	Standard CSV/TXT, no format restrictions

Features that do not exist are not included in the table. The table only includes capabilities that both parties have publicly disclosed. Magic Cube Data’s specific features may change with version updates; refer to official documentation for the latest.

---

Migration Step One: Exporting Number Lists from Magic Cube Data and Format Conversion

Common Export Formats from Magic Cube Data and Issues

Export files from Magic Cube Data are usually CSV or TXT, containing fields like: Phone Number, TG Registration Status, Active Days, Gender, etc. However, field naming may be inconsistent across different batches or export templates, for example:

• Magic Cube Data export column name: “Phone Number”, “Number” (pure digits)
• Format example: 13812345678 (without country code)
• Possibly mixed result columns: “Yes/No”, “1/0”, “Registered/Not Registered”

Before importing these lists into KK-DATA, two things need to be done: standardizing number format and cleaning irrelevant columns.

Converting Lists to KK-DATA Compatible Format (Three Steps)

Step 1: Ensure numbers include international country codes

KK-DATA supports numbers with or without the + sign, but it is strongly recommended to unify them into international format: +country code + phone number (e.g., +8613812345678). If your exported numbers from Magic Cube Data are pure digits (e.g., 13812345678), you need to:

• If all numbers are from the same country (e.g., China), use find-and-replace in a text editor to add +86 uniformly.
• If numbers are from multiple countries, you may need to handle them separately based on prefixes or known origins. KK-DATA’s “Global Number Screening” can directly recognize country codes (as long as the number starts with a country code, e.g., 86138...), but the format with + is more reliable.

Step 2: Delete irrelevant columns, keep only the number column

In Excel or a text editor, delete all non-number columns, leaving only a single column of pure number data. If you need to keep existing detection results for later comparison, save a copy separately, but the file submitted to KK-DATA for tasks only needs the numbers.

Step 3: Upload the list

KK-DATA provides two paths:

• Directly use “Global Number Screening”: Click “New Screening Task”, select the platform (e.g., Telegram), then upload your CSV/TXT file.
• First import into the “Global Number Generation” module: This module can generate new numbers or upload custom CSV. If you plan to supplement number segments via generation before screening, import the cleaned list as a “Custom Segment CSV”.

Both methods work. For pure list screening, the first method is recommended—upload directly for screening, simpler and more efficient.

---

Creating Migrated Screening Tasks in the KK-DATA Console

Selecting Task Type: From Magic Cube Data’s “Batch Detection” to KK-DATA’s “On-Demand Detection”

Tasks in Magic Cube Data are typically fixed as “Batch Detection”, processing all numbers with a predetermined package. KK-DATA’s task creation is more granular: you can create multiple tasks for the same batch of numbers, detecting different platforms and detection types separately.

For example, for a list of Chinese phone numbers, you can:

• Telegram registration detection (screen numbers already registered for TG)
• WhatsApp validity detection (screen WA numbers)
• RCS availability detection (optional, as per console availability)

A single task supports up to approximately 1 million numbers, covering most migration scenarios. The task creation interface will show:

1. Select detection platform: Telegram, WhatsApp, iMessage, RCS, etc.
2. Select detection type: e.g., “tg registered”, “tg valid”, “tg active (7/15/30 days)”, “tg gender identification”, “WhatsApp valid”, “wsid export”, etc.
3. Upload list: Supports CSV, TXT, one number per line.
4. Preview cost: The system automatically calculates estimated cost based on number count and detection type, and displays current balance.
5. Submit task: Can be submitted if balance is sufficient. If insufficient, you will be prompted to recharge.

Field Mapping Settings: Mapping Original Detection Result Fields to KK-DATA Output Fields

After migration, you need to become familiar with KK-DATA’s output field naming. Below is a mapping table to help you accurately match result columns from Magic Cube Data to KK-DATA’s export fields:

Magic Cube Data Common Field	KK-DATA Corresponding Field (as in Console)	Description
TG Registration Status	tg registered	Detects whether the number is registered on Telegram
TG Active or Not	tg active (7 days/15 days/30 days)	Need to select specific activity window
Gender	tg gender identification	Based on avatar recognition, default output: male/female/unknown
TG Account	tgid	Telegram unique ID, can be exported for subsequent targeted marketing
WA Account	wsid	WhatsApp Business account ID
WA Registered or Not	WhatsApp valid	Detects whether the number is valid on WhatsApp
(None)	RCS available	RCS (Rich Communication Services) detection, optional

---

Data Deduplication Warehouse: Avoid Wasting Balance on Repeated Detection

A common pain point with Magic Cube Data is difficulty in cross-task deduplication: numbers you have already detected may be charged again if uploaded again. KK-DATA has a built-in Data Deduplication Warehouse feature that automatically records all detected numbers (identified by number + platform + detection type). When you upload the same numbers in subsequent tasks, the system will prompt to skip duplicates, not consuming this task’s quota.

Best Practices for Migration:

1. Create a “Full List Deduplication Task” in KK-DATA – simply upload all your old numbers. The system will automatically compare with historical detection records and only detect undetected parts (on the first detection, almost all are new, so all will be detected).
2. For each subsequent addition of new numbers, first submit to the deduplication warehouse, then initiate a detection. This maximizes balance utilization.
3. For historically valid numbers migrated from Magic Cube Data (e.g., known as TG registered), you can save them separately as “known valid lists” for direct use without re-detection. Only submit numbers that need additional dimensions (activity, gender, etc.) for detection.

---

Exporting Results: Field Mapping Check and Multi-Format Output

Export Field Reference Table (Magic Cube Data → KK-DATA)

After a task completes, go to the result export page. KK-DATA supports custom export fields; you can check the columns you need. The following table helps you quickly select:

Result You Need	Fields to Check in KK-DATA
Whether the number has Telegram registered	tg registered (yes/no)
Number activity days	tg active (7/15/30 days, returns yes/no)
User gender	tg gender identification (male/female/unknown)
Telegram User ID	tgid
WhatsApp Account	wsid

Note: KK-DATA’s activity detection returns whether the number was active within the specified window, not the exact number of active days. If you need precise days, we recommend setting the window to the maximum of 30 days and estimating based on actual needs. If Magic Cube Data has an “active days” field, there is no exact equivalent in KK-DATA (unless customized), but you can approximate by conducting multiple detections with different windows.

Batch Export and Task Notification Settings

• Export format: Supports CSV, TXT, can be compressed to ZIP.
• Batch export: Supports downloading results of multiple tasks simultaneously.
• Task notification: When creating a task, you can check “Notify me via Telegram when task completes” and bind your Telegram account (via @kkdata_cc or console settings). You will receive result notifications without having to constantly monitor the console.

---

Migration Common Issues and Best Practices

• Question: How to handle large lists from Magic Cube Data (over 1 million records)?
  KK-DATA’s single task supports a maximum of 1 million records. If your list is larger, submit in batches. You can use Excel to split by time or region, then upload batch by batch.

• Question: Do I need to re-detect all historical numbers after migration?
  Not necessarily. If your detection results from Magic Cube Data are still usable, you can use them directly. Only re-detect if you need dimensions unique to KK-DATA (e.g., tgid, wsid, custom activity). Use the data deduplication warehouse to avoid duplicate charges.

• Question: How to supplement new numbers?
  KK-DATA’s “Global Number Generation” module supports random generation for 240+ countries/regions, global prefix generation, and custom segment CSV import. Generation is free; screening is charged per record. You can first generate a batch of target country numbers, then screen them uniformly.

Frequently Asked Questions

Q: Can numbers from Magic Cube Data be directly copied and used in KK-DATA?

A: Yes, but confirm that the number format is international (e.g., +country code + number). If Magic Cube Data exports pure digits or lacks country codes, it’s recommended to add prefixes via a text editor first, otherwise detection may fail. KK-DATA’s “Global Number Screening” supports numbers with or without +, but standardizing is strongly recommended. Use formats like +86% or +1%.

Q: What is the difference between KK-DATA’s billing and Magic Cube Data’s? Which is more cost-effective?

A: Magic Cube Data typically uses subscription or package plans with prepaid fixed fees; KK-DATA is a no-subscription, pay-per-record model. Which is more cost-effective in the long run depends on your number volume, detection types, and usage frequency. We recommend estimating based on actual needs (refer to real-time pricing in the console). KK-DATA is more friendly for users with low frequency or peak flexibility. If you regularly detect large numbers monthly, compare unit prices and decide.

Q: After migration, can the historical detection results from Magic Cube Data be imported into KK-DATA?

A: KK-DATA currently does not support directly importing historical detection results. You can only import number lists for re-detection, but you can use the data deduplication warehouse to avoid double charging for already detected numbers. We recommend saving the list of valid numbers from Magic Cube Data separately before migration, then importing them into KK-DATA for incremental detection. For known valid numbers, you can even skip detection and use them directly.

Q: Does KK-DATA support all detection types from Magic Cube Data?

A: Both support Telegram and WhatsApp detection, but KK-DATA additionally supports iMessage, RCS, empty number/carrier detection, etc. (subject to actual console availability). For activity detection, KK-DATA supports specifying custom windows like 7/15/30 days, while Magic Cube Data may only offer fixed tiers. Please compare the current feature lists of both platforms. If a certain detection type (e.g., precise active days) is not available on KK-DATA, it cannot be obtained via field mapping, and you may need to adjust your evaluation criteria.

Q: During migration, which console settings do I need to manually adjust?

A: Three main areas: 1) Format of the number list (ensure it includes country code); 2) Task creation – select the correct detection type (e.g., from Magic Cube Data’s “TG active” to KK-DATA’s “tg active (7 days)”); 3) Export field selection (based on the final fields you need). Detailed steps are in the H2 sections above. We recommend testing with a small list of a few dozen numbers in the console first to confirm mappings are correct before batch processing.

---

This concludes the complete guide to migrating number screening from Magic Cube Data to KK-DATA. If you encounter any issues during the process, please refer to the documentation, or contact customer support via @kkdata_cc for one-on-one assistance. Log in to the console now and experience the post-migration screening workflow!