Technology Services Directory: Purpose and Scope
Cloud migration encompasses a wide and technically diverse landscape — from lift-and-shift workload transfers to full application refactoring, from single-cloud deployments to multi-cloud governance frameworks. This directory exists to organize that landscape into a structured, navigable reference for technology professionals, procurement teams, and enterprise decision-makers operating within the United States. The scope spans cloud migration strategy, vendor selection, compliance alignment, and post-migration operations, with entries organized by technical category rather than commercial preference.
Standards for inclusion
Entries within this directory meet a defined set of criteria before publication. The standards are not aspirational — they reflect verifiable attributes tied to recognized classification systems and named public frameworks.
Listings are evaluated against four primary criteria:
-
Topical relevance to cloud migration — The subject must fall within the migration lifecycle as defined by frameworks such as AWS Migration Services Overview, Azure Migration Services Overview, or Google Cloud Migration Services Overview. Peripheral topics (generic IT consulting, unrelated SaaS products) are excluded by default.
-
Alignment with recognized technical standards — Content and vendor capabilities are assessed relative to published standards from the National Institute of Standards and Technology (NIST), specifically NIST SP 800-145, which defines cloud computing across five essential characteristics, three service models (IaaS, PaaS, SaaS), and four deployment models. Entries that cannot be mapped to at least one NIST-recognized model are not included.
-
US operational scope — The directory targets organizations operating under US jurisdiction. Regulatory references reflect US federal and state frameworks, including FedRAMP (administered by the General Services Administration), HIPAA (enforced by HHS Office for Civil Rights), and PCI DSS (maintained by the PCI Security Standards Council). Vendors or tools without documented US service capability are excluded.
-
Technical specificity — Entries must describe discrete technical functions rather than general service categories. A listing for Database Migration Cloud Options must distinguish between homogeneous migrations (same engine, different infrastructure) and heterogeneous migrations (different database engine), for example. Entries that cannot demonstrate this level of precision are returned for revision before publication.
The distinction between a strategy resource and a vendor listing is enforced throughout. Strategy pages (such as Cloud Migration Strategy Frameworks) provide framework-level guidance. Vendor listings document specific service providers, their documented capabilities, and the technical contexts in which those capabilities apply.
How the directory is maintained
Directory maintenance follows a structured review cycle rather than ad hoc updates.
Categorization is applied at intake. Each entry is assigned to one of the following technical domains: strategy and planning, infrastructure migration, application migration, data and database migration, security and compliance, tooling and automation, or post-migration operations. This taxonomy is aligned with the migration phases described in the AWS Cloud Adoption Framework (AWS CAF) and Microsoft's Cloud Adoption Framework (CAF for Azure), both of which are publicly documented by their respective publishers.
Technical review is conducted before any entry is published or updated. For compliance-sensitive categories — including HIPAA Compliant Cloud Migration, FedRAMP Cloud Migration Government, and PCI DSS Cloud Migration — entries are cross-referenced against the authoritative regulatory text before publication. No compliance claims are published without traceable source attribution.
Versioning is applied when a referenced standard changes. NIST Special Publications, FedRAMP authorization baselines, and PCI DSS versions are tracked; when a new version supersedes an older one, affected entries are flagged for revision within 60 days of the update's effective date.
Removal criteria are defined in advance. An entry is removed when: the referenced vendor ceases US operations, the underlying standard is withdrawn without replacement, or the technical content becomes factually irreconcilable with current platform capabilities (e.g., a deprecated migration tool that no longer receives vendor support).
What the directory does not cover
Defining scope requires explicit exclusion boundaries, not just inclusion criteria.
The directory does not cover general IT infrastructure consulting that lacks a specific cloud migration application. A firm that offers data center design services without a documented cloud transition methodology does not qualify for inclusion, regardless of technical depth.
Software-as-a-service product listings are excluded unless the SaaS product is itself the subject or vehicle of a migration workload. SaaS Migration Considerations addresses the migration context; it is not a product directory for SaaS vendors.
International-only providers — vendors with no documented US service presence, no US data residency options, and no compliance alignment with US federal frameworks — fall outside directory scope. The directory does not attempt to cover cloud migration as practiced under EU GDPR, UK data protection law, or Asia-Pacific regulatory regimes.
Training and certification programs are not listed as directory entries. While organizations such as the Cloud Security Alliance (CSA) and major hyperscalers publish certification pathways relevant to cloud migration, those programs are referenced within contextual pages rather than treated as directory listings.
Relationship to other network resources
This directory functions as the structural index for a broader set of reference resources. The Technology Services Listings page provides the navigable entry point for all categorized entries. For readers unfamiliar with how to navigate or interpret directory content, How to Use This Technology Services Resource provides operational guidance on filtering and interpreting entries by use case.
Deeper reference material — including the Cloud Migration Glossary, Cloud Migration Assessment Checklist, and Cloud Readiness Assessment — operates as supplementary reference content rather than directory listings. These resources are structured to support decision-making at specific stages of the migration lifecycle: pre-migration planning, mid-migration execution, and post-migration validation. The directory index links to these resources where topically appropriate, but does not merge them into the listing taxonomy.