Getting Started

How to announce a platform move without making customers do admin

Give buyers one reason, one action and one deadline, while handling account changes behind the scenes where possible.

The store.fan teamNovember 16, 20266 min read
How to announce a platform move without making customers do admin

Your customer opens an email, sees that your shop is moving, and is immediately asked to create a new account, download a new app, find their old receipt and update their payment details. You may have completed the move, but from their side you have handed them a small admin project. A better announcement gives each buyer one reason to care, one action to take and one date to remember.

Start with the change customers will notice

“I am moving platforms” describes your work, not the buyer’s outcome. It may be true that you are changing checkout software, hosting or membership tools, but those details rarely tell a customer what to do. Lead with the practical difference they will experience: a single place to find their downloads, a clearer course area, a new support address or a more reliable way to receive updates.

Write the announcement around one reason. For example: “Your course library is moving to one new home, where future lessons and updates will appear.” That sentence gives the move a purpose without asking customers to understand your backend. If there are several benefits, choose the one that changes their next visit. Put secondary details below the action rather than competing with it.

Reduce the move to one customer action

Choose the action by customer type. A one-off download buyer may only need the new product link. A course student may need to accept an invitation or sign in. A membership customer may need to confirm billing. Do not give all three groups the same vague instruction to “move your account”. Tell each group exactly what will happen when they click.

  1. 1Name the action in a verb: “Save your new library link”, “Sign in to the new course area” or “Update your payment method”.
  2. 2Give one direct route to complete it. Avoid sending people to a homepage where they must search for the relevant product.
  3. 3Say what they do not need to do. If you have already moved their files, say they do not need to buy them again or upload them again.
  4. 4Tell them what happens after the action, such as where future updates will be delivered.

Handle what you can behind the scenes

Before you write to customers, make a list of the objects that must move: product files, course lessons, member access, checkout links, receipts, support instructions and any promises about future updates. This is the operational work that prevents a simple announcement becoming a series of individual support requests. For a more detailed checklist, see how to map every file, licence and customer promise before leaving a platform.

Customer-facing itemPrepare before announcingTell the customer
Digital downloadUpload the current file and test the delivery linkWhere to get future files and updates
CourseCheck lessons, video access and the welcome routeWhere lessons now live and when access changes
MembershipConfirm access rules, renewal handling and support contactWhether they need to sign in or confirm billing
Old product pageAdd a redirect or clear notice where possibleThe new destination and the final date for the old one

A storefront on store.fan can give you one public home for products and links instead of asking customers to remember several disconnected destinations. You can use [store.fan’s digital downloads tools](/features/digital-downloads) for files, or its [online course tools](/features/online-courses) when the move includes structured lessons. The point is not to recreate every old screen. It is to make the next customer visit predictable.

Use one deadline, with a reason

A deadline is useful when it changes something real. “Please move by Friday” creates work without explaining why. “The old download page will stop receiving updates on Friday 30 August; save the new library link before then” connects the date to a consequence. Use an actual date and time zone if access, billing or support coverage changes.

The deadline should be late enough for customers to act, but not so far away that the move disappears from their attention. You decide that window from your own support capacity and the number of customer groups involved. If you cannot keep the old route available until the deadline, do not promise that you can. State the exact change instead.

Write the announcement in layers

The first few lines should work for someone reading on a phone. Put the reason, action and deadline there. Then add the information needed by customers who have an exception: active subscribers, people who bought more than one product, customers with a remaining coaching session or anyone who cannot access the new page.

  • Subject: “Your course library is moving on 30 August”
  • Reason: “You will find future lessons and updates in one new library.”
  • Action: “Sign in here and save the new link.”
  • Deadline: “Please do this by 30 August, before the old library stops receiving updates.”
  • Reassurance: “You do not need to buy the course again.”
  • Help: “Reply to this email if your access is missing, and include the email address used for your purchase.”

Repeat the message without changing it

Send the same core message through the channels customers already recognise: email, the old product page, your community announcement and the new storefront. Repetition is useful here because each channel catches a different part of your audience. Keep the action and deadline identical. Changing “save your link” to “create your account” halfway through makes it unclear whether the task has changed.

If you are moving to store.fan, the paid plans begin with a 14-day trial, and store.fan takes 0% of sales while Stripe’s own processing fee still applies. Money goes straight to your own Stripe account. Those details may matter to you while planning the move, but they are not automatically customer benefits. Mention them to buyers only if they change the checkout, receipt or payment experience they will actually see.

Usually, no. Prepare the new links, files, access rules and support route first. You can announce an upcoming move before launch when customers have a useful action to take, such as saving a preview link, but do not send them to an unfinished destination.

Say so plainly and explain why it is required. Give one sign-in link, state whether their existing purchase or membership will appear there, and provide a support route for missing access. Do not describe a new login as automatic account migration.

Keep a clear notice on the old route for as long as you can, pointing to the new destination. Maintain a simple record of unresolved access or billing cases, and answer those cases directly rather than sending another general announcement.

Plan your new storefront and give customers one reliable place to return to.

Start on store.fan
#platform-move#customer-support#migration#digital-products

Turn your knowledge into income

Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.