WIRED reported on March 28, 2025, that DOGE was assembling a team to move Social Security Administration (SSA) systems off COBOL, potentially to Java, on a timetable of “a few months.” The report, based on multiple unnamed sources, described a proposed migration—not a confirmed rewrite or a completed project. It also said the exact start date was unclear. The available sources do not establish the project’s status as of October 7, 2026.
What did the report say DOGE planned?
WIRED’s March 28, 2025 report said DOGE was assembling a team to migrate SSA systems away from COBOL, potentially to Java, within a few months. The project details came from unnamed sources, and WIRED said it was unclear when work would start. SSA did not immediately respond to WIRED at publication. The reporting does not show that DOGE began or finished the work.
The scale helps explain why the timeline drew attention. WIRED cited a 2016 SSA Office of the Inspector General finding that SSA infrastructure contained more than 60 million lines of COBOL. That is a historical estimate, not a current inventory. WIRED also cited an SSA modernization plan from 2017 that forecast roughly five years for modernization; that plan does not prove the work proceeded unchanged or establish a present-day timetable. WIRED’s report
Why would a rewrite matter to people receiving benefits?
WIRED described SSA’s core systems as supporting Social Security number issuance, benefit payments, and benefit calculations. A defect in a system handling those functions could have consequences beyond a website or office inconvenience: it could affect whether a person is paid, how much they receive, or whether an error is detected.
Recommended Free Tools
Sources quoted by WIRED raised risks including missed or incorrect payments, errors that are difficult to see, unexpected edge cases, and the testing burden of replacing long-running systems. One SSA technologist put the concern this way: “Of course, one of the big risks is not underpayment or overpayment per se; [it’s also] not paying someone at all and not knowing about it. The invisible errors and omissions.” Consultant Dan Hon warned about the consequences of attempting the migration quickly, including people not receiving benefits, receiving incorrect benefits or entitlements, or waiting a long time. These were concerns about potential risks, not evidence that this reported project caused an outage or payment error.
What does federal oversight tell us—and not tell us?
A June 2025 Government Accountability Office (GAO) report provides relevant context about SSA’s technology oversight, but it is not a status report on the reported DOGE migration. GAO found that SSA had generally defined processes for managing investments under development, while lacking a process for its investment review board to oversee investments already in operations. Those operations investments included maintenance, infrastructure, cybersecurity, management, and mission-support services.
GAO said operations investments accounted for about 90 percent of SSA’s roughly $2.2 billion in fiscal year 2024 IT spending. It also found incomplete implementation of some review practices for investments under development and incomplete performance documentation for three selected investments. GAO made seven recommendations, including improvements to oversight and performance evaluation; SSA agreed to all seven. Its review covered three selected disability-modernization investments, and GAO cautioned that the sample was nongeneralizable. The findings should not be treated as conclusions about every SSA investment or the DOGE proposal. GAO report GAO-25-107200
For scale, GAO reported that SSA program records covered more than 70 million beneficiaries and recipients. That is a different measure from WIRED’s separate reference to more than 65 million people receiving payments; the figures should not be treated as interchangeable. Neither figure estimates how many people would be affected by a hypothetical migration.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhat safeguards would matter in a major migration?
The sources do not establish which architecture or migration method DOGE selected. In general, the relevant question is not simply whether code is rewritten in a newer language, but whether the agency can demonstrate that services and calculations remain correct before and after changes. For a system this consequential, meaningful safeguards would include:
- Mapping scope and dependencies: Identify the applications, data, interfaces, and operational processes affected before changing them.
- Testing against known results: Compare outputs from the existing and replacement systems across routine cases and difficult edge cases, including historical records and benefit calculations.
- Running systems in parallel where feasible: Reconcile results before shifting live processing, and investigate discrepancies rather than assuming they are harmless.
- Planning continuity and rollback: Establish how payment operations would continue and how changes could be reversed if testing or live monitoring finds a serious defect.
- Reviewing security and privacy: Assess whether changes protect sensitive personal information and preserve access controls.
- Setting accountable oversight and service measures: Document who approves changes, how performance is evaluated, and what service outcomes would show that the migration is working.
These are evaluation criteria, not claims that the reported team adopted them. The GAO findings make governance and performance documentation especially pertinent, while the WIRED report and lawmakers’ concerns underscore the importance of testing and continuity.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What did lawmakers say?
In June 2025, Senators Elizabeth Warren and Ron Wyden urged safeguards against hurried, untested changes. Their letter said it was “essential that appropriate testing and safeguards be put in place” to prevent interrupted service or loss of critical data. The letter said SSA’s modernization plan had been updated the prior year and cited the reporting and experts’ concerns. It expresses the senators’ concern; it is not an independent engineering assessment or confirmation that a specific change disrupted benefits. Warren-Wyden letter
What is known about the project’s outcome?
The sources cited here establish that WIRED reported a proposed migration in March 2025 and that lawmakers later called for safeguards. They do not establish whether the project started, what systems it covered in practice, whether it was completed, or whether it caused any benefit interruption. The GAO audit addresses SSA investment-management processes, not the status or results of this specific proposal. There is also no supported failure-probability figure for the reported plan.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
