CIOPages
All RFP questions

RFP Questions · Commercial & Legal

Migration & exit questions to ask a software vendor

96 migration & exit questions for the RFI, the RFP and the finalists, with scoring guidance, in one Excel workbook.

What this module is for

These are the migration & exit questions to put to any software vendor, whatever the product does. Add them to an RFP next to the questions about the product itself.

What it covers. Questions on how you leave: data export formats and completeness, exit assistance, contract exit terms, wind-down support and verified deletion at the end of the contract.

A selection usually runs in three rounds. The module has questions for each:

  • RFI, to the long list. 27 questions screen out vendors that fall short.
  • RFP, to the shortlist. 33 questions ask for detail.
  • Deep dive, to the finalists. 36 questions ask for evidence.

Each question comes with why it matters, what a good answer looks like and the red flags. The workbook scores the answers 0 to 5, weights them and totals them by round and section.

3 questions from the module

From the RFI round. The first shows part of the guide each question carries; the workbook adds follow-ups, a response format, a weight and a score column.

1. List every category of customer data, configuration, and customer-generated artifact (e.g., prompts, fine-tuned model weights or adapters, embeddings, evaluation datasets, logs, audit trails) that a customer can export at any time during the contract.

Why it matters. Buyers need to know upfront what is portable and what is locked in. Export of source data does not guarantee export of derived artifacts that carry significant customer investment, and a gap there creates lock-in.

Good answer
  • Enumerates each data class with explicit in-scope/out-of-scope labels.
  • Explicitly includes fine-tuned weights or adapters where applicable.
  • Includes logs, evaluation datasets, and audit records.
Red flags
  • Vague claims that 'all customer data' is exportable without enumeration.
  • Excludes fine-tunes, embeddings, or logs without explanation.
  • Export limited to source uploads only.

2. Is the export schema documented in a public, versioned specification, and how are breaking changes to the schema communicated and supported?

Why it matters. With an undocumented or silently changing export schema, the customer cannot build reliable downstream pipelines.

3. What exit assistance or transition services do you offer (e.g., dedicated migration engineer, data-mapping support, parallel-running period), and which are included in a standard subscription versus billed separately?

Why it matters. Exit-assistance scope and billing terms determine whether wind-down is a manageable project or an open-ended cost center.

What the module covers

  • Data export formats, scope & SLA (21)
  • Schema & format portability (18)
  • Exit assistance & wind-down support (22)
  • Contract exit terms & deletion verification (35)

This module is one of 6 in Commercial & Legal. All 6 in one workbook: $499

Questions about this module

How many migration & exit questions are there?

96: 27 for the RFI stage, 33 for the RFP and 36 deep-dive questions for the finalists.

What comes with each question?

Why it matters, what a good answer looks like, the red flags, follow-up questions, the response format, whether most buyers treat it as mandatory, and a suggested weight for scoring.

Which license do I need?

The Enterprise License covers any number of evaluations inside one organization. The Consultancy License covers use with any number of clients. Neither allows reselling or republishing the questions.

Included in these RFP packages

Each package carries this module's screening questions next to its questions about the software.

Related

Keep reading

Buyer Guide
Cloud Migration & Modernization Platforms
Free calculator
Cloud Egress Cost Calculator

An Excel calculator for cloud egress cost, the break-even and payback for a dedicated link, and a month-by-month projection.

Free canvas
Legacy System Replacement Map

A canvas for replacing a legacy system in pieces: find its seams, map the dependencies and order the cut-overs.