To switch swag providers safely, separate the new store launch from the old program’s closeout. Give every open order, employee balance, artwork file and remaining inventory item a named owner and a documented destination before changing the employee-facing link.
A new storefront can look finished while the migration is still incomplete. A welcome gift may be in production with the previous provider. An employee may have an unused award. A familiar jacket may require a new embroidery sample. Those obligations do not disappear when the new homepage goes live.
This checklist is for an existing company merchandise program moving to another provider—not a first-time launch. Its goal is continuity: employees know where to shop, finance knows what is still owed, and the incoming provider receives a usable operating brief.
Publisher perspective: Brand Sauce publishes this guide. The process below is an editorial recommendation, not a promise that Brand Sauce or another provider supports every transfer described. Confirm migration scope, export availability, fees and responsibilities in writing. Primary sources were checked September 19, 2026.
1. Define what the switch must fix
Start with the reason for changing providers. “We want a better store” is too broad to test. “Employees should not need HR to resolve ordinary ordering questions” creates a concrete support requirement. “We want less prepaid inventory” creates a different production and funding requirement.
Write three acceptance criteria and the evidence needed for each. For example: an employee can select an eligible gift without an administrator placing the order; finance can associate a test purchase with the correct department; an order question reaches the agreed support owner. These are suggested tests, not platform capabilities.
Keep unrelated changes out of the initial cutover. Replacing the provider, redesigning the brand, changing award values and launching internationally at the same time makes discrepancies harder to diagnose. Record those ambitions, but distinguish migration requirements from later improvements.
2. Build one handoff register
Use a shared register with an owner, current status, next action and evidence link for each item. Keep sensitive records in an access-controlled system rather than attaching employee lists to a broadly shared project document. The table below describes the minimum categories to resolve.
| What is moving or closing | Decision to document | Evidence before cutover |
|---|---|---|
| Open orders and returns | Who completes delivery, replacements and refunds? | Order-level exception list and support contacts |
| Employee awards and balances | Honor in the old store, replace, or transfer if supported? | Reconciled ledger with an approved treatment for each balance type |
| Artwork and decoration | Which files can be released and which need recreation? | Approved asset package and new production proof |
| Stored merchandise | Use down, transfer, retain, or dispose of appropriately? | Physical count, condition and receiving agreement |
| Employee information | What does the new provider actually need? | Approved field list, access and retention plan |
| Store links and access | Where will existing bookmarks and invitations lead? | Tested links and a clear transition notice |
Assign one internal migration lead who can resolve conflicts between these workstreams. The provider may manage setup, but someone inside the company must approve the treatment of an employee award or an old inventory purchase.
3. Keep old orders with a clear fulfillment owner
Choose a cutoff for new orders in the outgoing store. Record its time zone, not just the date. Then export or obtain a final order report at the cutoff and reconcile anything submitted during the transition window.
The simplest operating arrangement is often to let the original provider finish orders it has already accepted while the new provider takes new purchases. Do not assume this arrangement is available after contract termination; agree on the service period, access and fees before giving notice.
Track exceptions separately: items awaiting approval, backorders, undelivered shipments, damaged goods, return requests and refunds in progress. A shipment notification is not the same as a closed support case. Each exception needs an owner and a next review date.
Avoid copying an old order into the new store merely to make reporting look complete. Without a controlled process, that can create a second production instruction. If an order truly must move, document cancellation or release from the original provider before authorizing replacement fulfillment. Preserve the relationship between the original reference and the new one.
4. Reconcile balances before issuing replacements
Do not treat every number labeled “credit” as the same thing. A prepaid company account, a promotional code, an employee-funded purchase credit and an employer-funded gift allowance can have different terms. Ask finance and the relevant provider to identify what each represents before choosing a migration treatment.
Create a ledger containing the balance reference, authorized recipient where needed, currency, amount, last reconciliation time and proposed resolution. Check the applicable terms and obligations before changing access or deadlines. A technical cutover date does not itself decide what happens to someone’s entitlement.
Illustrative example, not customer data: suppose a program has $1,000 of outstanding employer-funded allowances. Finance approves replacement allowances totaling $800 and keeps $200 redeemable in the old store. Those two destinations should reconcile to the original $1,000. They are not $1,800 of new available value. A later redemption in the old system must not also remain available as a replacement.
Prevent double redemption with a documented cutoff and reconciliation process that both providers can actually support. If balances cannot be transferred, say so plainly and communicate the approved alternative. Use the same ownership discipline described in our guide to department-level company-store budgets.
5. Transfer approved artwork, not just a logo thumbnail
Ask for the assets the incoming decorator needs: approved logo versions, vector artwork where available, color references, decoration dimensions, placement notes and photographs of accepted samples. Include restrictions such as minimum logo size or which mark belongs on dark garments.
Confirm ownership and release rights for production files, including embroidery digitization. Paying for an earlier order does not tell you what files your contract allows you to receive. If an asset cannot be released, budget for recreation and proofing instead of discovering the gap after launch.
Font files need separate attention. Adobe’s packaging guidance explains that Adobe Fonts cannot simply be packaged and transferred to another user; collaborators needing the fonts require their own access or suitable license. Send a rights-cleared artwork package and ask the designer which editable assets may be shared.
Reapprove decoration on the actual replacement garment. A familiar logo does not guarantee an identical result on a different fabric, color or production setup. Our embroidery-versus-printing guide explains the garment and artwork decisions worth checking. Treat the approved sample, not a screen mockup alone, as the reference for the new production arrangement.
6. Give remaining inventory its own plan
Switching to an on-demand store does not make existing boxes disappear. Obtain a count by item, color, size, decoration and condition. Separate available merchandise from units reserved for orders. Ask whether storage, pick-and-pack, transfer freight or disposal charges remain after the store closes.
Then choose deliberately. Usable stock may serve a planned event or a limited use-down campaign. A receiving provider may accept it only under specific conditions—or not at all. Get receiving requirements, handling costs and ownership of discrepancies agreed before arranging a shipment.
Do not force a no-inventory model onto every requirement. Bulk can remain appropriate for a confirmed event quantity or a fixed kit specification. A hybrid arrangement can retain those uses while moving unpredictable individual demand to on-demand production. The migration should improve the program, not require abandoning useful merchandise to make the model sound purer.
7. Move only the employee data the new workflow needs
Start with the destination workflow, then identify necessary fields. A new invitation process may need an employee identifier and work email; it may not need years of historical shipping addresses. Confirm what must be preserved internally for reconciliation instead of sending the incoming provider the entire archive.
The FTC’s business guide to protecting personal information recommends inventorying information, keeping only what is needed, restricting access and setting a retention policy. Apply that discipline to migration exports: approve the recipient and transfer method, limit access, and decide when temporary copies will be removed.
Have IT and the provider agree on account setup rather than moving passwords through spreadsheets. Where a program uses single sign-on or automated eligibility feeds, test the new configuration and assign someone to retire the old connection after dependencies are resolved. These are requirements to verify, not assumptions that either platform supports a particular integration.
8. Run a small pilot with explicit stop conditions
Test more than whether a product can be added to a cart. Choose participants representing the program’s actual paths: a new recipient, someone with a replacement allowance, a department approver if applicable, and a buyer at a relevant delivery destination.
- Eligibility: the intended person gets access, and an ineligible test account does not.
- Funding: the correct allowance or payment method applies, with shipping and tax treatment visible.
- Ordering: the selected size, decoration and delivery details survive into confirmation.
- Recovery: an invalid entry gives a useful explanation and a way to correct it.
- Fulfillment: a representative test order arrives and matches the approved expectations.
- Reporting: finance can connect the transaction, funding source and any refund.
W3C’s form-notification guidance calls for understandable feedback about errors and successful completion. Include those states in the pilot, especially on mobile and when navigating by keyboard. A checkout that works only on the happy path is not a complete acceptance test.
Define what postpones launch: unresolved balance discrepancies, incorrect artwork, failed eligibility controls, or no agreed support owner. Cosmetic refinements can have a follow-up list. Failures affecting who receives what need resolution before broad invitations.
9. Publish a clear cutover message and keep a fallback
Employees need a short explanation of what changes, when it changes and where to get help. Avoid making them infer which provider handles a missing package from an old order.
Adaptable message structure: “Use [new store link] for orders placed after [date, time and time zone]. For orders already placed, contact [old-order support]. Your existing award will be handled as follows: [approved treatment]. If you cannot access the new store, contact [support].” Fill in verified details before using it.
Inventory the links in onboarding documents, intranet pages, recognition templates, saved QR codes and recurring messages. If an old URL cannot redirect, agree on a transition notice where possible. Test from an employee’s perspective, not only from an administrator’s signed-in browser.
Keep an operational fallback: pause new invitations, show a help message, or temporarily route approved requests through a controlled support process. Reopening both stores with spendable balances is not a safe default. Resume only after the migration lead understands which transactions occurred during the interruption.
Once the pilot passes, use the relevant final checks in our company-store launch checklist. Close the old program only when exceptions, records, invoices and agreed data handling are resolved—not simply when the new store is announced.
Frequently asked questions
Can employee gift balances move automatically?
Do not assume so. Ask both providers what the balance represents, whether exports and imports are supported, and how duplicate use will be prevented. If a transfer is unavailable, finance must approve another treatment and employees need clear instructions.
How long should switching providers take?
Use milestones instead of an unsupported universal timeline: accepted export, reconciled balances, approved decoration, delivered pilot and resolved cutover dependencies. Contract notice periods, outstanding orders and sample production can determine the schedule even when storefront setup is quick.
Must we replace the entire assortment?
No. Preserve useful products where availability, decoration and commercial terms work. Reapprove substitutions rather than describing a similar-looking item as identical. A smaller verified assortment is a sensible starting point while additional products are evaluated.
What should we ask an incoming provider first?
Ask for a written responsibility map: what it can import, what it will recreate, what remains with your team, and what the outgoing provider must finish. Then ask for acceptance evidence and itemized migration costs. A clear handoff is more useful than a broad promise that switching will be easy.
