Cloud Migration Discovery: Qualify the Project Before You Quote

A cloud migration opportunity is ready for a serious proposal when the customer can explain why the move matters, which workloads are involved, who owns the decision, and what must be learned before committing. A request for a cloud quote is a starting point. It does not establish migration readiness or permission to promise a delivery date.

AWS distinguishes an identified prospect from a customer-validated qualified opportunity. AWS Partner Central opportunity stages. AWS readiness guidance includes gathering stakeholders, documenting findings, and agreeing next steps. AWS migration readiness assessment process. The practical workflow below is a proposed management approach, not a claim that a particular tool or provider produces guaranteed results.

Separate buying intent from technical readiness

Run two connected conversations. The commercial conversation establishes the business trigger, funding process, timing, alternatives, and stakeholders. The technical conversation establishes environment constraints, dependencies, access requirements, and delivery risks. The account owner connects the findings, but a qualified technical lead validates the migration approach.

A buyer can be commercially serious while technically unprepared. A team can also be technically ready without an approved purchase. Record both states. Otherwise an enthusiastic architecture session can make a weak opportunity appear more advanced than it is, or a genuine buyer can receive a proposal that hides unresolved dependencies.

Use a qualification record with six decisions

Begin with the event that caused the conversation. A data-center exit, application change, resilience concern, or contract renewal gives context, but ask the customer to confirm the consequence of doing nothing. Avoid turning a technology preference into an assumed business case.

• Business outcome: what needs to improve, and who will judge it?
• Workload boundary: what is included, excluded, or still unknown?
• Decision group: who approves funding, architecture, security, and implementation?
• Timing: which date is fixed, and what depends on meeting it?
• Readiness evidence: what information exists, and who can provide missing inputs?
• Next commitment: what will both parties do before the opportunity advances?

Write short answers in the opportunity record. Link to supporting material rather than copying confidential configuration into an unrestricted sales note. If the customer cannot supply an answer, assign an owner to obtain it. An unknown is useful when it is visible; it becomes a problem when a proposal treats it as settled.

Choose the right next step

Use three routes. A well-understood, suitable workload can move toward validated scope. A potentially suitable project with material unknowns needs an agreed discovery or readiness exercise. An opportunity with no owner, credible need, or willingness to engage should remain in early qualification or be closed with a recorded reason.

Do not make every prospect attend a large assessment. A small, bounded migration may need a proportionate review. Equally, do not skip discovery because the customer asks for a fast number. Explain which assumptions a preliminary estimate depends on and what would change it. Keep estimates distinguishable from an approved commercial offer.

Protect the specialist team's time

Before inviting an architect, prepare a brief containing the buyer's desired outcome, candidate workloads, known constraints, questions requiring technical judgment, and the intended result of the meeting. Ask the specialist to confirm that the available evidence supports a useful session.

The sales owner should lead the buying process and document commitments. The architect should lead technical validation. Both can attend the same call without duplicating responsibility. A meeting that produces additional questions is not necessarily a failure; the important test is whether the unknowns are smaller and the next action has an owner.

Illustrative example: a deadline without a workload inventory

Suppose a hosting customer wants to leave a facility before its lease ends. The owner asks your team for a fixed migration quote, but the application inventory is incomplete and nobody has confirmed acceptable interruption windows. These are hypothetical circumstances, not an Escencion client result.

The appropriate next step is to agree what inventory and business input are needed, appoint the customer's application owner, and have your technical lead define a bounded discovery activity. The sales record can show an active project with readiness gaps. It should not show a committed implementation date simply because the lease date is known.

After discovery, return to the buying group with the validated boundary, unresolved exceptions, responsibilities, and the proposal decision required. If the customer cannot provide necessary inputs in time, discuss alternatives openly rather than silently compressing technical work.

Review progression using evidence

In the pipeline meeting, ask what changed since the previous review. New evidence could be a confirmed sponsor, accepted discovery scope, validated workload group, or scheduled commercial review. Another internal email is activity, but it is not automatically progress.

Useful operating measures include the proportion of qualified opportunities with a customer-confirmed next step, time waiting for customer inputs, and proposals returned for scope correction. Define each measure before comparing periods. Review reasons for disqualification too; a pattern can reveal that outreach is attracting the wrong projects.

What should the owner change first?

Choose one recent proposal that became difficult after submission. Reconstruct which business and readiness questions were unanswered. Add those questions to your intake record, then test the revised process on the next relevant opportunity. Keep the record small enough that the sales team will use it and specific enough that the technical team can trust it.

Put clear ownership around the work

Escencion provides Managed Sales & Business Operations for technology companies. Our current client focus is MSPs and MSSPs. Explore our Managed Sales approach, or discuss the responsibilities you need managed. Your technical team retains technical validation, approved commitments, engineering, and service delivery.