When a collectible-toy brand replaces its loyalty or retail system, customers notice whether they can sign in, whether their points are correct, and whether coupons and launch reservations still work. Migration must connect identities, preserve promised benefits and retain trustworthy data for future loyalty activity.
Member counts and point totals alone are insufficient. Duplicate accounts, cross-channel identities, coupon states, tier validity, limited-event eligibility and tag origins can produce errors in individual accounts even when overall totals match.
Decide which member data remains operational
Identities, current tiers, valid points, unredeemed coupons, active reservations or limited entitlements and necessary authorisation records support login and benefit calculations and belong in the new system. Determine the depth of historical purchase and interaction migration from customer-service, tagging and analysis needs. Retire and archive unexplained, stale or unnecessary data under the agreed rules.
For each field, record its name, business meaning, source, update time, purpose, migration method and acceptance owner. Clarify whether “point balance” means available points, lifetime points or a balance including frozen points. Determine whether “valid coupons” excludes locked coupons, redeemed codes and refunds in progress.
Stored value and prepaid accounts require separate balance, frozen-amount and financial-responsibility checks. Do not combine them with points. Limit personal-data migration to defined purposes and necessary fields, with role permissions and records for export, transfer, import, exception handling and disposal.
Resolve identities before combining benefits
Phone numbers, membership cards, WeChat OpenID and UnionID, e-commerce accounts and legacy IDs may refer to one person or conflict because of shared numbers, changed numbers or input errors. Define the primary identity in the target system and how other identifiers link to it.
Do not automatically merge accounts solely by phone number. Address different names sharing one number, multiple platform accounts and registrations after account closure. Specify which profile survives and how tiers, points, coupons and purchase history combine. Preserve original-to-new account links for stores and customer service.
Assess password compatibility separately. If encryption methods differ, do not export or reconstruct plaintext passwords. Use SMS verification, renewed login or password reset, with customer communications and service procedures ready before launch.
Snapshot all benefits at an agreed cut-off
Entitlements change during trading. At the cut-off, snapshot identity, tier, growth value, available and frozen points, expiry dates, each coupon’s state and scope, and reservation or limited-event usage.
| Entitlement | Confirm before migration | Acceptance check |
|---|---|---|
| Tier | Current tier, progression and downgrade rules, validity | Tier counts and representative accounts match |
| Points | Available, frozen, expired and soon-to-expire definitions | Totals, distribution, expiry and individual balances match |
| Coupons | Unclaimed, issued, locked, redeemed and expired states | Valid coupons redeem; invalid ones cannot be reused |
| Reservations and limited benefits | Launch reservations, member-only purchase eligibility and usage | Valid eligibility continues; consumed eligibility is not restored twice |
| Authorisations | Source, time, channels and current state | Scope matches the intended subsequent use |
Mark reservations or limited benefits “not applicable” where the brand does not use them. Keep stored value and prepayments in separate financial snapshots and reconciliation.
If consumers can earn or spend during cutover, extract incremental changes and define exactly when the old calculation ends and the new one starts. Check redeemed coupons awaiting status transmission and already-used reservations before final extraction to avoid duplicate use.
Check the reliability of IP and collection-preference tags
Tags may describe IP, series or character preferences, collection depth, purchase frequency and participation in releases. Keep them only when source, update time and calculation rules are explainable.
Recalculate from reliable history where rules have changed. Retire unexplained or outdated tags and rebuild them from new transactions and interactions. Reassess sensitive information and free-text notes before allowing them to support audience selection.
The loyalty team should be able to explain why a member has an IP-preference tag, what evidence produced it and the calculation cut-off. A technically successful import does not make an unexplained tag suitable for targeting.
Reconcile totals and inspect individual accounts
Trial samples should include high-point and multi-coupon members, duplicate identities, recent tier changes, cross-channel accounts, limited-benefit holders and inactive members. Use them to expose mapping, merge and entitlement-state problems, recording revisions and discrepancies.
Before cutover, complete at least one full or near-full-volume rehearsal. Reconcile total and active members, tier counts, point totals and distributions, coupon counts by state and reservation eligibility. Then inspect risk-based samples individually. Matching totals with benefits assigned to the wrong accounts is still a failed migration.
- Phone, card and WeChat identifiers resolve to the correct account.
- Merges follow agreed rules, with original accounts and evidence traceable.
- Available points can be queried, redeemed and expired correctly; frozen or invalid points remain unusable.
- Valid coupons redeem; redeemed, expired or store-ineligible coupons are restricted.
- Tiers and benefits match, and progression and downgrade rules continue.
- Valid reservation and limited eligibility remain usable; consumed rights are not incorrectly restored. Non-applicable cases are marked.
- IP and other tags have identifiable origins; unsuitable legacy tags do not drive selection.
Include the entitlement snapshot in overall migration acceptance
PEKON CRM covers identities, tags, tiers, points and coupons. OneID connects stores, mini-programs, e-commerce and adviser touchpoints within the same brand. Identity merges, historical benefits and channel binding still depend on source data, authorised scope and project configuration.
Classify requirements as standard functionality, configuration, integration, custom development or unsupported. Support for historical imports does not mean every legacy rule transfers unchanged.
Limited-product benefits also depend on orders and stock. Review the companion guidance on pre-orders, collection and returns, and on PDQ, complete-box and individual-unit inventory. Include identity rules, entitlement snapshots and account checks in the supplier-acceptance package.
The member-entitlements section of the collectible-toy migration checklist can help organise a common-cut-off snapshot. Contact PEKON to clarify OneID, points, coupons, limited eligibility or stored-value boundaries.
Frequently asked questions
Is importing member profiles enough?
No. Verify tiers, points, coupons, reservations, limited eligibility, identity links, login methods and necessary authorisations. Customers must be recognised and able to use valid benefits.
Can duplicate members be merged by phone number?
Not universally. Shared or changed numbers and historical errors require checks against membership cards, WeChat identifiers, registration channels and purchases, with conflict and manual-review rules.
Is matching the points total sufficient?
No. Check tiers, distribution, expiry and frozen status, then inspect high-value and exceptional accounts. Totals cannot prove correct allocation.
What is commonly missed in coupons and limited eligibility?
Locked coupons, pending refunds and redeemed codes awaiting updates; reservations, consumed rights and cancellations that should not restore eligibility. Align state definitions and test valid and invalid benefits.
Can stored value migrate together with points?
Do not combine them. Stored value and prepayments require separate balances, frozen amounts, payment or refund responsibility and financial reconciliation. Points follow the brand’s loyalty rules.