Portfolio conversion readiness diagnostic
7 checks for the timing, operations and activation risks of a defined conversion wave.
Read the framework ↓Support planning only: below 15K cards, self-led; 15K–under 50K, specialist input; 50K or more, coordinated delivery. These are illustrative scope bands, not service packages, cost estimates or readiness rules. Confirm actual capability and complexity.
Conversion parameters
Verification applies to this approach and wave only. Changing the approach resets it.
Diagnostic results
What this is
A portfolio conversion — whether a network switch, product upgrade, or M&A migration — is one of the highest-stakes programs an issuer undertakes. It touches every function, every customer, and every system simultaneously. The standard approach is a 200-line project plan that obscures which dimensions are genuinely at risk until it is too late to course-correct.
Seven readiness checks expose release prerequisites and unresolved work. Portfolio size also suggests a support scope; that guidance is separate from release readiness.
Three layers of conversion readiness
- Timeline — Does the chosen approach have a workable schedule and buffer? Size informs planning and support scope, not a standalone release gate.
- Operational Readiness — Can the issuer execute across strategy, IT, logistics, and compliance? These workstreams fail independently.
- Risk & Activation — Will the conversion retain customers, and is there a post-conversion program to capture the EMOB activation window?
Conversion types
| Type | Description | Complexity |
|---|---|---|
| Network switch | Domestic or competitor scheme to new network | High |
| Product upgrade | Standard to premium within same scheme | Medium |
| M&A migration | Acquired portfolio reissued under buyer brand | High |
| Scheme consolidation | Multiple schemes consolidated to single network | Medium |
Conversion approaches
| Approach | Mechanism | Risk profile |
|---|---|---|
| Forced | All cards replaced on set date | Highest — maximum coordination required |
| Opt-out | Auto-converted unless customer declines | Moderate — requires clear notification |
| Opt-in | Customer actively chooses to convert | Low per card; risk of low conversion rate |
| On-expiry | Converted at natural renewal | Lowest disruption; longest total timeline |
The 7 diagnostic rules
Timeline (Rule 1), operational readiness (Rules 2–5), and risk / activation (Rules 6–7). Resolve legal and route-evidence prerequisites before generic rule counts.
| # | Rule | Tests |
|---|---|---|
| 1 | Timeline feasibility | Is there enough time for the chosen conversion approach? |
| 2 | Strategy & segmentation | Is there a segment-level conversion strategy with KPIs? |
| 3 | IT & data readiness | Are systems tested and the route-specific inclusion / exclusion files verified? |
| 4 | Logistics & fulfillment | Is card production and staged delivery confirmed? |
| 5 | Regulatory & compliance | Are all legal and regulatory requirements cleared? |
| 6 | Attrition risk | Is projected churn within acceptable range? |
| 7 | EMOB activation readiness | Is there a 90-day post-conversion activation program? |
How to use
Set the conversion profile, assess operational readiness on each dimension, and input risk estimates. Rules evaluate in real time. Load a preset to see how different scenarios produce different verdicts. Start with failing rules — those are the blockers to address before proceeding.
Constructed comparison: open prerequisites
Use the open-prerequisites preset: 75,000 cards, opt-out approach, 10 months and a dedicated PMO. Strategy and logistics are scored 4; IT and early activation are 3. Compliance is In Progress, route evidence is Unverified and expected attrition is 4.5%.
| Rule | Status | Detail |
|---|---|---|
| R1 — Timeline feasibility | ✓ Pass | 10 months less the 7-month assumption leaves 3 months of buffer |
| R2 — Strategy & segmentation | ✓ Pass | Score 4 — segment plan in place |
| R3 — IT & data readiness | △ Watch | Score 3; route evidence unverified — tests and list reconciliation remain open |
| R4 — Logistics & fulfillment | ✓ Pass | Score 4 — vendor confirmed |
| R5 — Regulatory & compliance | △ Watch | In progress — not yet cleared |
| R6 — Attrition risk | ✓ Pass | 4.5% — within the demonstration attrition band |
| R7 — EMOB activation readiness | △ Watch | Score 3 — basic plan, no milestones |
Hold execution: 0 failures and 3 warnings. A three-month buffer passes the timeline check, but compliance and consent/list evidence are still open. Additional calendar time does not resolve those prerequisites.
What this demonstrates
The seven checks expose timing, operational and activation assumptions for a named wave. A small portfolio with adequate internal capability can use self-directed support and still pass readiness; support scope does not authorize execution.
When the conclusion changes
This is a release screen for a defined portfolio wave. Legal clearance and consent / list evidence are prerequisites, not points that other workstreams can offset.
Trace one cohort through consent, inclusion / exclusion, migration, delivery, activation and use. Confirm exception owners and rollback evidence; none of these checks guarantees retention.
How these assumptions were set
Scenario construction
The prepared wave uses 175K cards and 16 months, giving four months above the assumed 12-month baseline. The open-prerequisite example uses 75K cards, opt-out and 10 months, giving three months above seven. The compressed case deliberately leaves a negative buffer. These are planning exercises, not recorded conversions.
Why these bands
The month table assumes coordinated waves need more preparation than expiry-led waves; larger waves and missing coordination add time. The exact months, 100K size break, 5/10% attrition bands and 15K/50K support bands are retained planning assumptions, not delivery or vendor benchmarks. Support bands never determine readiness.
Test the sensitivity
A two-month buffer warns and a three-month buffer passes the timeline check. Neither can clear missing consent/list evidence or compliance approval. Compare a wave of 10K versus 50K with the same readiness evidence: the support prompt may change, but size alone cannot hold release.