# Should DISA reopen competition for the Combatant Command migration?

**URL:** <https://community.iquasar.com/t/should-disa-reopen-competition-for-the-combatant-command-migration/598>\
**Category:** \#DebateThis\
**Tags:** govcon\
**Created:** [July 31, 2026, 4:36am UTC](https://community.iquasar.com/t/should-disa-reopen-competition-for-the-combatant-command-migration/598 "2026-07-31T04:36:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![farrukhshah](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.iquasar.com/farrukhshah/32/409_2.png) [@farrukhshah](https://community.iquasar.com/u/farrukhshah)\
**Post date:** [July 31, 2026, 4:36am UTC](https://community.iquasar.com/t/should-disa-reopen-competition-for-the-combatant-command-migration/598/1 "2026-07-31T04:36:53Z")

</div>

![DISA](https://canada1.discourse-cdn.com/flex031/uploads/iquasar/original/1X/4d60c34448dd9fc0e986166a192d1a5e5ecc91a8.jpeg)

Should DISA reopen competition for the Combatant Command migration effort, or is expanding an existing vehicle the fastest path to mission success?

**Argument FOR DISA’s Review:**

- The migration affects approximately **231,000 users across 200 locations worldwide** , making it one of the most consequential DoD network modernization efforts underway.
- Conducting market research after the protest creates an opportunity to validate assumptions, assess alternative capabilities, and strengthen acquisition integrity.
- Competition can often uncover innovative approaches, reduce risk, and improve long-term value for taxpayers.

**Argument AGAINST Delaying Execution:**

- DoD has directed DISA to migrate combatant commands to the DoDNet environment, and the agency has a target of completing the effort by **30 September 2028**.
- Delays in acquisition strategy decisions can impact mission timelines and increase uncertainty for stakeholders.
- The challenge is not just procurement. It is executing a highly complex migration while maintaining operational continuity.

**From my perspective,** the real question is not whether DISA should move fast or compete fairly. It must do both. In mission-critical IT modernization, speed without scrutiny creates risk, while scrutiny without execution creates delay. The winning strategy is a transparent acquisition approach that accelerates delivery without sacrificing competition.

**What do you think?** Should DISA pursue a new competitive path, or was leveraging the existing DES contract the right move from the start?

**Source:** [Federal News Network Article](https://federalnewsnetwork.com/contracting/2026/07/disa-seeks-industry-input-on-combatant-command-migration-after-gdit-protest/) [[federalnew…etwork.com]](https://federalnewsnetwork.com/contracting/2026/07/disa-seeks-industry-input-on-combatant-command-migration-after-gdit-protest/)

---

<div class="post-metadata">

**Author:** ![Iram\_Sehar](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.iquasar.com/iram_sehar/32/165_2.png) [@Iram\_Sehar](https://community.iquasar.com/u/Iram_Sehar)\
**Post date:** [August 3, 2026, 9:50am UTC](https://community.iquasar.com/t/should-disa-reopen-competition-for-the-combatant-command-migration/598/2 "2026-08-03T09:50:10Z")

</div>

It doesn’t have to be an all-or-nothing choice between a 2-year delay or a sole-source expansion. DISA could utilize a hybrid approach: leverage existing enterprise frameworks for baseline DoDNet onboarding, while competitively soliciting specialized task orders or sub-tier requirements—like Thunderdome Zero Trust integration, ICAM, and theater-specific operational edge capabilities. This maintains execution momentum on common commodity IT while opening up mission-critical specialized work to competitive market capabilities.