A replatforming RFP asks implementation partners how they would move your store: what data goes where, how it is checked, how launch and recovery work, and who is responsible for each part.
The generator builds a migration register, an integration register and a launch search checklist from your answers. Unknowns such as account portability or the rollback point stay visible as decisions for discovery.
Your answers stay on your device. The generator runs in your browser: nothing you type is uploaded or stored on our servers, there is no account, and nothing goes to suppliers unless you send the files yourself. Site analytics count page visits, steps reached and downloads, never what you type.
What this RFP covers
Discovery before a fixed price
If the destination platform or major integrations are undecided, the RFP asks for a separately priced discovery phase and marks implementation estimates as provisional.
Data and balances
Each object in the migration register gets its own plan, count, cleansing owner and reconciliation method. Gift card, credit and loyalty balances reconcile by currency.
Search at launch
Where URLs change, the RFP covers mapping, redirect testing and monitoring. Where they do not, it still asks for checks on status codes, rendering, indexability and internal links. It does not ask for a traffic guarantee.
Cutover and recovery
Bidders explain their freeze or delta approach, how orders taken during cutover are handled, and the last safe rollback point. Rehearsal results are delivered after appointment, not demanded in proposals.
Responsibilities
A responsibility matrix records who is accountable for data cleansing, integration mapping, technical SEO, QA and launch approval. "Shared" needs a named lead.
Question areas used: business, outcomes and scale; current technology and ownership; integrations; replatforming, data and cutover; agency scope, delivery and governance; security, accessibility and governance; timetable, costs and selection. Specialist areas such as B2B, subscriptions or several markets appear only when your answers make them relevant.
Some of the questions it asks you
M02What is changing besides the platform?Changes to domains, URLs or structure carry more search risk than a like-for-like move.
M03What data and content should move, stay accessible elsewhere, be archived or be retired?
M07Can customer accounts and passwords move to the new platform?Passwords often cannot be transferred, which means customers must reset them. Only the platforms involved can confirm this.
M12How will imports avoid triggering customer emails, fulfilment, refunds, automations or duplicate reporting?Importing old orders can accidentally send emails or create shipments if automations are left on.
M18Which cutover approach do you prefer?A freeze stops changes during the move; a delta migration moves late changes afterwards; a phased cutover moves parts of the business in stages.
M21What rollback or recovery must be demonstrated, including transactions created after cutover?If launch has to be reversed, orders taken on the new site still need handling.
M24When can the old platform and its contracts safely be retired, and who approves that?
Every question can be answered, marked unknown, not applicable, or kept private.
What suppliers send back
A migration and cutover approach with assumptions per data object
A delivery plan with phases, deliverables and your dependencies
A named team with allocations and comparable migrations
A pricing schedule separating discovery, build, migration and stabilisation
How proposals are compared
Default criteria and weights in the private evaluation workbook. Editable before you issue the RFP; they are starting points, not a standard.
Understanding of our migration
15
Delivery, integration and cutover approach
25
Validation and reconciliation
20
Proposed people and relevant experience
15
Whole-life cost and commercial clarity
15
Ownership, support and exit
10
Scores show coverage until every criterion is assessed. A failed eligibility gate excludes a supplier whatever its score.
Worked example
Migration for an Australian retailer. 20,000 products, several warehouses, ERP retained, gift card balances, historical orders and URL changes. Account portability and rollback are unresolved. The business is fictional.
Implementation and migration. For implementation partners and agencies.
Buyer
Wattlebrook Outdoor (fictional)
Issue date
Not yet issued
Revision
1
Generated
2026-10-20 09:00 UTC
1. Executive brief
Wattlebrook Outdoor (fictional) invites proposals for the following work package: Implementation and migration (Implementation or build, Migration).
What prompted this project: The legacy platform reaches end of support in 2027 and cannot run the second warehouse's stock rules.
Priority outcomes: Move without losing order history or gift card balances.
How ready are you for proposals?
Ready for proposals
How settled is the choice of future platform?
Selected
Which platforms or editions are selected or shortlisted, and is that a preference or a fixed constraint?
NovaCart Enterprise (fictional), selected after a separate evaluation. Fixed constraint.
2. Business context
How do you sell?
Direct to consumer (B2C)
What do you sell?
Physical products
Which countries, languages, currencies, brands and storefronts are in scope?
Country or region
Language(s)
Currency
Australia
English
AUD
How many active products and sellable variants exist?
Active products: 20,000 products
Do customers hold gift card, store credit or loyalty balances with you?
Yes
Priority outcomes
Outcome
Target status
Move without losing order history or gift card balances
No numeric target
3. Current environment and constraints
Systems in scope
System
What it does
Status
Criticality
ERP
Stock, purchasing, finance
Must stay
Critical to trading
Warehouse system, Melbourne
Fulfilment
Must stay
Critical to trading
Warehouse system, Brisbane
Fulfilment
Must stay
Critical to trading
Gift card service
Issue and redeem gift cards
Needs assessment
·
What platform, edition or version and storefront approach do you use today?
LegacyShop 4 (fictional), self-hosted
4. Work packages, scope and exclusions
Work package
Services
Addressed to
Implementation and migration
Implementation or build, Migration
Implementation partners and agencies
14 more sections in the full document.
Frequently asked questions
What should a replatforming RFP say about SEO?
It should ask for the method: URL inventory, mapping and redirect decisions, testing on staging and at launch, and a monitoring period with an owner for fixes. Search results can fluctuate after a move, so acceptance is based on the agreed checks, not a promise of no traffic loss.
Can I ask bidders for migration rehearsal results?
Not at proposal stage. Bidders explain their rehearsal method and relevant experience; the appointed supplier produces actual rehearsal and reconciliation results during delivery.
What if I do not know whether customer passwords can move?
Mark it unknown. The RFP then asks suppliers how they would confirm portability with the platform and payment providers, and what the contingency is if it is not available.