Technology Services Listings

The listings compiled within this directory cover technology service providers, platforms, tools, and frameworks relevant to cloud migration planning and execution across the United States. Each entry is organized to support structured evaluation rather than promotional comparison. Understanding how entries are structured, what data points are included or omitted, and where verification gaps exist allows practitioners to apply directory information accurately within their own procurement and planning workflows.

How to read an entry

Each listing follows a standardized schema designed to surface decision-relevant facts without editorial ranking. The schema aligns with the service classification taxonomy used by NIST in SP 800-145, which defines cloud service models as Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). Entries are labeled with one primary model designation and, where applicable, a secondary model when a provider spans categories.

A standard entry contains the following ordered fields:

1. Provider or tool name — the registered trade name or product name as publicly listed by the vendor
2. Service model classification — IaaS, PaaS, or SaaS per NIST SP 800-145 definitions
3. Migration relevance category — one of: assessment, lift-and-shift, replatforming, refactoring, data transfer, or governance
4. Primary deployment geography — US-only, North America, or global, based on published service region documentation
5. Compliance posture indicators — flags for FedRAMP authorization status (sourced from the FedRAMP Marketplace), HIPAA eligibility, and PCI DSS attestation where publicly documented
6. Tool type — agent-based, agentless, managed service, or self-hosted

Entries covering major hyperscaler-native tooling reference platform-specific documentation. For provider-by-provider breakdowns, see the dedicated pages for AWS Migration Services, Azure Migration Services, and Google Cloud Migration Services.

The migration relevance category is the primary filter practitioners should apply first. A provider strong in assessment tooling — such as cloud readiness scoring or dependency mapping — may carry no replatforming capability. Conflating these categories is a documented source of vendor selection failures noted in cloud-migration-common-mistakes.

What listings include and exclude

Listings cover providers and tools that meet 3 baseline criteria: (1) the provider operates documented US service regions, (2) at least one publicly available datasheet, pricing page, or technical specification exists, and (3) the service maps to at least one phase of a recognized migration framework such as the AWS Migration Acceleration Program or the Azure Cloud Adoption Framework.

Included:
- Hyperscaler-native migration services (e.g., AWS Application Migration Service, Azure Migrate, Google Migrate for Compute Engine)
- Third-party managed migration service providers with published US customer references
- Open-source migration tooling with active GitHub repositories and documentation updated after 2022
- Compliance-specialized integrators holding current FedRAMP or HITRUST certifications

Excluded:
- Providers operating exclusively outside US jurisdiction
- Tools listed only in vendor-assembled marketplaces without independent technical documentation
- Consulting firms offering migration advisory without proprietary tooling or a disclosed methodology
- Products in end-of-life or sunset status as indicated by vendor announcements

The exclusion of pure advisory firms without tooling is a deliberate boundary. Migration execution involves tooling dependencies that pure consultancies cannot satisfy independently. Practitioners evaluating managed cloud migration services will find that the most capable providers combine proprietary tooling with delivery capacity.

Listing inclusion does not constitute endorsement and does not reflect pricing negotiability, contract terms, or support quality — variables that are not publicly verifiable at the directory level.

Verification status

Entries carry one of 3 verification tiers based on the evidence trail available at time of compilation:

• Documented — information sourced directly from vendor technical documentation, government databases (e.g., FedRAMP Marketplace, SAM.gov), or standards body registries
• Attributed — information sourced from third-party analyst reports or press releases; not independently cross-checked against primary documents
• Unverified — provider included based on market presence signals; specific field data not confirmed

Compliance posture indicators carry the highest verification burden. FedRAMP authorization status is cross-referenced against the live FedRAMP Marketplace database, which the General Services Administration maintains. HIPAA eligibility flags are sourced from vendor Business Associate Agreement (BAA) availability disclosures — not from HHS enforcement records, which reflect past findings rather than current eligibility. For compliance-sensitive deployments, the cloud-migration-compliance-us-regulations reference page provides the regulatory framework context that directory flags alone cannot supply.

Entries verified at the Documented tier are re-evaluated on a 12-month cycle. Attributed and Unverified entries are flagged for review when substantive changes to a provider's service scope or regulatory standing are identified through public channels.

Coverage gaps

The directory acknowledges 4 systematic gaps that affect completeness:

1. Regional and boutique providers — Firms operating within single US states or metropolitan markets are underrepresented. A Texas-based managed service provider with deep legacy system cloud migration experience may not appear if its documentation footprint is limited to local business directories.

2. Sector-specific integrators — Healthcare, defense, and financial services have specialist integrators whose migration tooling is proprietary and not publicly documented. Coverage of HIPAA-compliant cloud migration providers and FedRAMP-authorized solutions is more complete than general commercial sectors, because federal marketplace databases provide structured public records.

3. Emerging tooling categories — Containerization and serverless migration tooling evolves faster than directory refresh cycles. The containerization-cloud-migration and serverless-migration-strategy categories carry the highest proportion of Attributed-tier entries.

4. Pricing and contract data — List pricing is excluded from entries because enterprise cloud migration contracts are routinely negotiated below list rates. The cloud-migration-cost-estimation framework page addresses cost modeling methodology without relying on directory-sourced figures.

Practitioners working in sectors with regulatory specificity — financial services subject to PCI DSS, federal agencies subject to FedRAMP, or healthcare organizations subject to HIPAA — should treat directory listings as a starting filter and validate compliance posture directly against the authoritative registries maintained by the relevant oversight bodies.