Subscription management guide: migrating subscriptions from another CRM, and whether payment credentials can move

Open
#59 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation, payments

Research direction

Start with the subscription management guide, then read docs/agent-eval/probe-matrix-2026-09-16.md and the linked Shopify and Sticky transcripts to identify the unanswered migration questions. Done means the guide has a migrating-existing-subscriptions section covering preserved data, prerequisites, gateway-specific credential handling, and when to contact NEXT.

Written by the indexing model from the issue text.

Description

Gap: the subscription management guide documents creating and importing subscriptions, but not the migration case: bringing active rebills over from Sticky.io, Checkout Champ, Recharge or Konnektive, and in particular whether stored payment credentials (vault tokens) can be migrated or whether customers re-enter cards.

How it surfaced: the agent consultation probes for nextcommerce-site#154 (2026-09-16). Every funnel/CRM and Shopify+Recharge persona, on both Claude and Codex, named credential portability as the gating question for the migration and put it in the open questions as "unverified". It is the first thing a subscription-heavy merchant needs to know and it is not on the page.

Ask: a "Migrating existing subscriptions" section: what the import path preserves (prices, renewal dates, gateway assignment), what it needs, and the honest answer on payment credentials by gateway (token migration where a processor supports it, re-collection otherwise). If the answer is "talk to NEXT", say that on the page so agents route the question rather than guess.

Evidence: probe matrix, shopify transcript, sticky transcript.

Dominant language
MDX
Stars
2
Forks
0
Avg merge
6h 4m
Merged PRs (30d)
13

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NextCommerceCo/developer-docs

All issues in NextCommerceCo/developer-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.