In short
- Definition: The ease with which a system can be moved from one hardware, software or hosting environment to another.
- Goal: Avoid lock-in and lower the cost of changing platforms.
- Example S.M.A.R.T. requirement: Deployment to a new cloud provider in under 10 person-days with no code change outside the configuration layer.
1. Definition
As a non-functional requirement, portability describes how easily a system can be moved from one hardware, operating system, cloud provider or hosting environment to another [1], [2].
Portability is an exit door. You may never use it, but you negotiate better knowing it is there.Key takeaway
In the 2011 edition of ISO/IEC 25010, portability was a top-level characteristic [3]; in the 2023 edition it was replaced by flexibility, which keeps related ideas such as adaptability, installability and replaceability.
Portability is helped by standard technologies, containers, infrastructure as code, configuration kept outside the code, and avoiding provider-specific services where they are not essential. The Twelve-Factor App, for example, recommends a clean contract with the operating system for maximum portability between environments [4].
2. Goal
The goal is to avoid lock-in and to lower the cost and risk of changing platforms, providers or data centers.
Without it, a price increase, an end-of-support notice or a change of strategy can force a costly rewrite.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Effort to move to a new provider | Person-days | < 10 with no code change outside the configuration layer | Migration rehearsal |
| Provider-specific services used | Count | Only those listed and justified | Architecture review |
| Environments supported by the same build | Count | All target environments | Automated tests per environment |
| Data export | Format and time | Complete export in an open format within 24 h | Export test |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Cloud exit: “The application shall be deployable to a second cloud provider in under 10 person-days, with no code change outside the configuration layer, verified by a yearly rehearsal.”
- Containers: “All services shall be packaged as standard OCI containers and run on any conformant Kubernetes platform.”
- Data: “All business data shall be exportable in an open, documented format within 24 hours.”
5. Questions to Ask Stakeholders
- How likely is a change of platform or provider in the system’s life?
- Which provider-specific services are worth the lock-in?
- Which environments must be supported now?
- How will data be exported if we leave?
- Who decides on exceptions to portability rules?
- How often should a move be rehearsed?
6. Common Pitfalls
- Portability at any cost. Avoiding every managed service can cost more than lock-in. Decide case by case.
- Forgetting data. Code is portable, but proprietary data formats may not be.
- Never testing a move. Untested portability is an assumption.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Flexibility — replaced portability as a top-level characteristic in ISO/IEC 25010:2023.
- Adaptability — fitting new environments.
- Dependency on Other Parties — portability reduces supplier lock-in.
- Platform Compatibility — running on several user platforms.
8. FAQ
The 2023 edition replaced portability with flexibility as a top-level characteristic, keeping related sub-characteristics.
They help a lot, but databases, managed services and configuration must also be portable.
A situation where leaving a supplier is so costly that the customer is effectively stuck.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010 for software quality. Its short name comes from the Greek “isos” (equal) and is said as a word. | [5] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [6] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [7] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [8] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [2] |
| OCI | Open Container Initiative | Industry project that defines open standards for container images and runtimes. | [9] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Cloud | Computing resources (servers, storage, services) rented over the internet from a provider. | [10] |
| Container | Package that bundles an application with everything it needs to run, isolated from other software. | [11] |
| Data center | Building that houses servers, storage and network equipment. | [12] |
| Data migration | Moving data from one system or format to another. | [13] |
| Database | Organized store of data that software can query and update. | [14] |
| Deployment | Installing a new version of software in the environment where people use it. | [15] |
| Infrastructure as code | Defining servers and networks in versioned files instead of configuring them by hand. | [16] |
| Kubernetes | Open-source system that runs and manages containers across many machines. | [17] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [18] |
| Vendor lock-in | Dependence on one supplier that makes switching costly or difficult. | [19] |
10. Sources and Further Reading
- [1] “Software portability.” Wikipedia. https://en.wikipedia.org/wiki/Software_portability (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “ISO/IEC 25010 product quality model.” ISO 25000. https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 (accessed Nov. 18, 2026).
- [4] 12factor.net. “The Twelve-Factor App.” The Twelve-Factor App. https://12factor.net/ (accessed Nov. 18, 2026).
- [5] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [6] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [7] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [8] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [9] “Open Container Initiative.” Wikipedia. https://en.wikipedia.org/wiki/Open_Container_Initiative (accessed Nov. 19, 2026).
- [10] “Cloud computing.” Wikipedia. https://en.wikipedia.org/wiki/Cloud_computing (accessed Nov. 19, 2026).
- [11] “Containerization (computing).” Wikipedia. https://en.wikipedia.org/wiki/Containerization_(computing) (accessed Nov. 19, 2026).
- [12] “Data center.” Wikipedia. https://en.wikipedia.org/wiki/Data_center (accessed Nov. 19, 2026).
- [13] “Data migration.” Wikipedia. https://en.wikipedia.org/wiki/Data_migration (accessed Nov. 19, 2026).
- [14] “Database.” Wikipedia. https://en.wikipedia.org/wiki/Database (accessed Nov. 19, 2026).
- [15] “Software deployment.” Wikipedia. https://en.wikipedia.org/wiki/Software_deployment (accessed Nov. 19, 2026).
- [16] “Infrastructure as code.” Wikipedia. https://en.wikipedia.org/wiki/Infrastructure_as_code (accessed Nov. 19, 2026).
- [17] “Kubernetes.” Wikipedia. https://en.wikipedia.org/wiki/Kubernetes (accessed Nov. 19, 2026).
- [18] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [19] “Vendor lock-in.” Wikipedia. https://en.wikipedia.org/wiki/Vendor_lock-in (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @silverkblack; inline photo by @element5digital, both on Unsplash.








