On this page
A storefront migration can leave a reward campaign technically alive but practically unreachable. The customer’s receipt points to an old offer page, the new account shows a different order number, and support searches the new store while the original promise sits in an archived folder.
The commercial handoff needs its own cutover register. It should connect what the customer saw before migration with the route they can use afterward. This article addresses that customer promise, rather than the code or database work required to move a store.
Identify the customer-facing references that will change
Take a hypothetical homeware merchant moving from an older storefront to a redesigned Shopify store. A campaign has already generated 80 qualifying purchases. Some customers are waiting for an eligibility decision; others need to complete the approved claim process. The migration team plans to retire the old campaign page on the same evening it launches the new site.
Inventory every reference an earlier purchaser may still possess. Include the purchase confirmation, offer URL, campaign name, visible order reference, account entry, support email, and any printed insert. A page is not the only route into the promise. An email sent weeks ago may be the most important document the customer has.
For each item, identify whether it changes, remains available, or becomes inaccessible. Do not label a reference “migrated” merely because the underlying data was copied. The customer may still be unable to recognize the new reference or use it to obtain help.
Separate order identity from offer identity. The same customer can have one order under an older campaign and another under a newer offer. Sending both orders to a generic page showing the latest reward amount can rewrite the apparent promise, even when the internal records remain correct.
Preserve access to the offer attached to each purchase
Create a promise register before the cutover. The following filled example uses fictional references and proposed routes; it does not imply a particular RebateCardX migration feature.
| Existing reference | Customer route after cutover | Promise preserved | Accountable owner |
|---|---|---|---|
| Old campaign page, Spring Home V1 | Readable historical offer page | Original eligibility and reward wording | Marketing operations |
| Order OLD-1042 | Support lookup connects OLD-1042 to the retained purchase record | No need for the customer to guess a new identifier | Store operations |
| Existing reward instruction email | Its destination remains valid or explains the approved next route | Existing claim assistance remains understandable | Reward operations |
| Old account bookmark | Migration notice explains the available order-history route | The customer is not told to repurchase | Customer experience |
| Open support case CASE-18 | Named queue and new case owner retain the earlier correspondence | Previously stated follow-up is visible | Support lead |
Preserve the historical wording as a record, with a clear label explaining which purchases it covers. A retained page should not look like an invitation to join a closed campaign. Conversely, a closed-campaign notice should not suggest that every existing reward has ended.
The RebateCardX Shopify integration overview describes the connection between purchase context and the reward journey. A migration plan should verify the actual approved integration scope rather than assume the platform automatically resolves changed storefront references.
Rehearse the register from the customer’s starting point. Give a reviewer an old confirmation email and ask them to find the applicable offer and assistance route after the proposed cutover. Do not let the reviewer begin inside the merchant dashboard. The exercise is valuable precisely because customers lack that internal context.
A difficult case involves an order placed just before the cutover while an offer update goes live immediately afterward. Record the effective time and the policy that determines which offer applies. Support needs a reproducible answer, including the relevant time zone, rather than an informal rule that “new store means new terms.” Resolve the boundary before the first customer asks.
Decide when new campaign invitations can resume
Treat resuming new invitations as a separate decision from maintaining existing promises. The new storefront may be ready to sell products while its reward pages, account links, or support lookup still need attention. In that case, preserve the existing journey and delay the next campaign invitation until the commercial path is clear.
Define evidence for restarting: an earlier purchaser can find the historical offer; a new purchaser sees only the current offer; support can connect both order-reference formats; and the approved reward route works in the new customer journey. These checks concern what people can understand and do, not merely whether a deployment completed.
Assign a cutover owner to unresolved gaps. For example, if an old email cannot be changed, the destination it contains may need to remain available. If the new account cannot show an earlier order, publish an accurate alternative assistance route instead of implying that the order never existed.
Prepare a concise customer notice when a material route changes: “Your earlier purchase remains associated with the offer shown when you ordered. You can use your original order reference when contacting us through this service page.” Replace the proposed wording with the actual approved process, and avoid asking customers to send card credentials as proof.
After the migration, sample recent support contacts involving old references. Repeated confusion can reveal a broken handoff that a launch rehearsal missed. Keep the historical promise route available for the appropriate period determined by the merchant’s obligations and program arrangements; do not choose a retention period solely because the redesign team wants to remove old pages.
The cutover is commercially complete when an earlier customer can still explain what they were offered, identify the purchase, and reach the responsible team. A new storefront should change the shopping experience without making the original reward promise disappear.
Discuss the campaign continuity requirements of your planned Shopify migration. Discuss campaign fit.
Source references
This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.