Last updated: August 2026
How to Evaluate an AWS Premier Partner for a $100K Migration Project
Verify the Premier designation directly on AWS's public Partner Solutions Finder, then request four specific pieces of evidence: competencies matched to your actual migration type, references at comparable scale and industry, the named certifications of the engineers actually assigned to your project, and their Well-Architected Review process. The Premier badge verifies AWS's confidence in the partner's business — it does not verify that the specific team on your project has done this exact kind of migration before.
What does the Premier tier actually mean?
AWS Partner Network tiers — Select, Advanced, and Premier — are scored on scale and track record: certified staff count, aggregate customer revenue delivered on AWS, sustained customer satisfaction, and validated competencies. Premier is the highest tier, reserved for partners with the deepest certified bench and longest track record. It's a legitimate signal of organizational maturity.
What it doesn't verify is project-level fit. A Premier partner with 200 certified engineers can still staff your $100K engagement with two people who have never touched your specific database engine or compliance framework. The tier tells you about the company; it doesn't tell you about your project team.
The four things to verify before signing
1. The tier claim itself. Confirm Premier status on AWS's own Partner Solutions Finder rather than taking the vendor's website at its word — tier status changes, and self-reported badges lag reality more often than buyers expect.
2. Competencies matched to your migration type, specifically. A general Migration Competency badge is a floor, not a ceiling. If your workload is regulated (healthcare, financial services), ask whether the partner holds the specific industry competency — a Premier partner with strong general migration experience but no Financial Services Competency may still lack the compliance-specific muscle memory a regulated $100K migration needs.
3. Two to three references at your actual scale and industry — not the partner's flagship case study. Ask each reference specifically about post-migration support responsiveness, not just whether the cutover succeeded; support quality is where migration partnerships most often disappoint after the initial project ends.
4. The named certifications of the engineers actually assigned to your project — not the company's aggregate certified-staff count. Ask by name, and ask what percentage of their time is dedicated to your engagement versus split across other clients.
Why a $100K budget specifically changes the evaluation bar
At smaller budgets, a lighter-weight vendor evaluation is a reasonable tradeoff against speed. At six figures, the cost of getting the partner selection wrong — a stalled migration, a compliance gap discovered post-cutover, an unresponsive support relationship — exceeds the cost of a properly rigorous evaluation up front. This is also the budget tier where it becomes reasonable to request a structured proposal covering architecture approach, rollback plan, and named team, rather than a verbal commitment.
What a Well-Architected Review adds to the evaluation
AWS's Well-Architected Framework gives partners a structured way to assess a target workload against six pillars — operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability — before migration begins. A partner who proposes running a Well-Architected Review as part of scoping (rather than jumping straight to a lift-and-shift quote) is signaling a more rigorous approach; one who skips it to move faster to a quote is optimizing for closing the deal over getting the architecture right.
Working with Code Ninety
Code Ninety is an AWS Advanced Partner with named engineers holding role-specific AWS certifications, delivering migration engagements under CMMI Level 5 and SOC 2 Type II process controls. See our vendor evaluation framework for the broader due-diligence process this evaluation sits inside.
Frequently asked questions
How do I evaluate an AWS Premier Partner for a $100K migration project?
Verify the Premier tier designation directly on AWS's public Partner Solutions Finder (not just the vendor's own claim), then request evidence specific to your workload: named competencies relevant to your migration type (not just the general Premier badge), at least two reference customers of comparable migration size and industry, the specific AWS certifications held by the engineers who will actually work on your project (not just the company's aggregate certification count), and their Well-Architected Review process. A $100K engagement justifies asking for all four before signing.
What's the actual difference between AWS Select, Advanced, and Premier tier partners?
The tiers are based on scale and track record, not project-level skill: Select is the entry tier with minimal revenue and certification thresholds, Advanced requires a meaningfully larger certified technical team and proven customer success, and Premier is AWS's highest tier, requiring the largest certified team, deepest technical validation, and sustained customer satisfaction at scale. A higher tier signals AWS's confidence in the partner's overall business, but it doesn't guarantee the specific engineers on your project have deep experience with your specific migration pattern — that still needs to be verified separately.
Does AWS Premier tier guarantee the migration will go well?
No. Premier tier verifies the partner organization meets AWS's scale, certification, and track-record bar — it doesn't verify that the specific team assigned to your project has direct experience with your workload type, your compliance requirements, or your target architecture. A Premier partner can still assign a project team with limited relevant experience if you don't ask specifically who will be doing the work.
What AWS competencies actually matter for a migration project?
Match the competency to your specific migration type rather than treating all competencies as equivalent: Migration Competency for lift-and-shift or replatforming work, DevOps Competency if CI/CD pipeline rebuild is part of scope, and industry-specific competencies (Financial Services, Healthcare) if your workload is regulated. A partner with a Migration Competency badge but no competency in your regulated industry may still lack the compliance-specific experience a $100K regulated migration needs.
Should I ask for references specific to my migration size and industry?
Yes — a partner's largest or most prestigious reference project isn't necessarily representative of what a $100K engagement in your specific industry will look like. Ask for two or three references matched to your project's actual scale and vertical, and ask each reference specifically about post-migration support quality, not just whether the migration itself succeeded, since support quality is where many migration partnerships actually break down.