Digital-product migration has an entitlement problem. A file may copy successfully while prior buyers lose access, links expire incorrectly, or an unprotected URL exposes the download. Test what a purchaser can access and what support can restore.
How to make the decision
List each downloadable product, file version, license terms, access duration, download limit, customer entitlement and support reset path. Confirm whether the destination can import historical entitlements or whether the team needs a separate secure archive. Use test accounts representing a recent purchase, an expired entitlement and a refunded order. Check authenticated access, link expiry, file integrity and mobile download. Keep source files protected during the transition and remove old public links only after a verified replacement exists. Record where the customer will ask for help.
Worked example
Synthetic course store moves 40 files and 300 prior purchases. The files open for new buyers, but a past buyer’s account shows no downloads. The team maps historical order IDs to the new entitlement system and tests a prior purchaser. A refunded buyer can still download, so the team fixes refund revocation. A file checksum confirms the protected PDF is intact. The release note explains what prior customers will see.
What to verify
- Can prior purchasers access what they paid for?
- Are refunded or expired accounts blocked correctly?
- Are file versions and limits intact?
- Does support have a restore procedure?
Limits and ownership
Do not place licensed files in a public media folder to solve access problems. Keep entitlement decisions with the product owner and test privacy controls.
What to hand over
Give support a secure entitlement lookup with product, source order, allowed file version and expiry rule. Keep the mapping behind access controls. A past buyer should receive a clear route to restore access; the team should not ask them to repurchase a file they still own.
Common question
Is moving the file enough?
No. The customer’s right to access the file, expiry rule and support path must move or be recreated too.
Next useful step
Use How to Test Search and Filters After a Catalog Import for the adjacent decision. For an implementation review, see Megvi’s ecommerce website development service and bring the source records, proposed checks and open exceptions.
Source checked 28 October 2026: WooCommerce: product import fields for downloads. Check current platform settings before changing a live store or report.
The worked example is illustrative and is not presented as a Megvi client outcome.