Independent, not SAM.gov

SAM.gov IAE migration: what the read-only weekend means for contractor

Updated 6 October 2026

ZeroGov tracks SAM.gov as one lane of US federal contracting, not as the system itself, and the Independent Award Environment cutover on Oct 6, 2026 was the first live test of that move. Before any deep dive, the disclaimer: ZeroGov is independent and is not SAM.gov, the IAE, GSA, or the IRS. Nothing on this page is a substitute for your Entity Administrator reading the official IAE release notes. What follows is a plain chronology and a checklist you can run the moment the system accepts writes again.

What actually changed on Oct 6, 2026

SAM.gov stopped accepting writes at 8:00 p.m. Eastern on Sunday Oct 5, 2026. The site stayed readable, which is why the read-only weekend feels familiar to anyone who lived through prior renewal seasons, but the search and read APIs returned a different header set. GSA flipped the cutover shortly after noon Eastern on Monday Oct 6, 2026, and the system resumed registration, modification, and renewal work on the new Integrated Award Environment stack.

For the first wave, three buckets moved: entity records, the representations and certifications block, and the exclusions extract. Opportunity posting, FPDS reporting, and the FSRS subaward flow stay on the old SAM.gov for now, with staged cutovers through December 2026. If you tried to file a bid or submit a subaward report over the weekend, the system queued it rather than rejected it, and the queue drained once writes returned.

ZeroGov is independent, not SAM.gov, and the IAE migration is the kind of event where the official release notes matter more than any third party explainer. The independent read you can get here is the timing, the scope, and the order in which small contractors tend to hit problems when the system comes back up.

The read-only weekend, hour by hour

The cutover schedule circulated by the IAE programme office runs in four blocks. Friday Oct 3, 2026 was a soft freeze: writes worked but mirrored to both stacks so the new environment had a baseline. Saturday Oct 4, 2026 was reconciliation, with the data team comparing entity, reps, and exclusions counts between stacks. Sunday Oct 5, 2026 from 8:00 p.m. Eastern was hard read-only, the window most contractors noticed because they could not push a renewal.

Monday Oct 6, 2026 was go-live. The IAE flipped the load balancer before the 12:00 p.m. Eastern target and writes resumed. The afternoon was stabilisation, with the IAE throttling heavy users first, so a corporate admin doing 200 entity updates at once sat in a longer queue than a one-off small business. By Tuesday morning, the throttle relaxed, and the IAE confirmed that the first 24 hours showed no rollback.

Two small things contractors reported in the first hours, both worth checking. First, the login screen served a new banner for about 40 minutes that asked users to confirm whether they had a Login.gov account before they touched the entity form. That banner is the same nudge ZeroGov has run for two years; it is now official copy. Second, the case tracker kept its old numbering, so a ticket you opened on Saturday under a 10-digit number is still findable, but the case view itself is faster because the IAE has dropped a slow Oracle join that used to time out on older records.

What migrated in wave one, and what did not

Wave one was narrow on purpose. Entity records, including UEI, legal business name, physical address, mailing address, banking addendum, and points of contact, all moved. The representations and certifications block, including the FAR 52.212-3 and the FAR 52.219 family, moved with them, and so did the exclusions list, which is now served by the IAE exclusion service rather than the older SAM extract. CAGE assignments continued to stream from the DCAA portal into the new stack without a contractor-visible change.

What did not move in wave one matters just as much. Opportunity posting on the contract opportunities side is still on the old SAM.gov, with a separate cutover window in late November 2026. FPDS reporting, the Federal Procurement Data System, stays where it is through the end of the year. FSRS, the subaward reporting system, has a wave two slot in early December 2026. CPARS, the past performance system, is untouched. eSRS, the executive compensation reporting, is untouched. If a contracting officer told you a system cutover would affect FPDS on Oct 6, they were misreading the schedule.

The point of the phased cutover is to let the IAE prove the entity data layer first, since every other system depends on it. A bad entity record poisons FPDS and FSRS at the same time, so getting the foundation right is the unglamorous priority. Wave two, in late November 2026, will pull opportunity posting across, and wave three in December 2026 will pull subaward and executive compensation across.

What to verify the moment the system accepts writes again

Run a four-step check before you touch anything else. Step one, log in through Login.gov and confirm you land on the new dashboard. The old domain still resolves, but the cutover means the data is served from the IAE host. If the URL bar still says the legacy host, clear cache and retry; a stale DNS record is the most common reason a contractor thinks the migration did not land.

Step two, open your entity record and compare every field to the PDF you saved on Oct 4, 2026, the last clean export before the freeze. Pay close attention to the address block, the banking addendum, and the points of contact, because the migration is the moment small typos become active. A wrong routing number on a 60-day-old record has been known to slip past renewal and into the new stack because nobody re-read the page.

Step three, open the reps and certs block and check the FAR 52.219-1 small business set-aside representation, the 52.219-2 women-owned or economically disadvantaged representation, and any HUBZone or 8(a) cross-references. The reps block is a frequent target of the IAE's new validation service, which now flags inconsistent size and socioeconomic flags. A small business marked both 8(a) and HUBZone without the right cross-reference triggers a soft warning, and the soft warning now blocks save until you resolve it.

Step four, search the exclusions list for your own UEI and for the UEIs of every subcontractor you carry on active awards. The exclusions extract moved with the migration, and it is the first chance in a year to confirm the public list still matches your internal watch list. If a subcontractor shows up on the active exclusions list, you have a duty to report under FAR 52.222-50, and the cutover is a clean moment to do the audit before the year-end rush.

Why the IAE exists, in one paragraph

The Integrated Award Environment is the federal government's effort to put every award-related system behind one identity, one data layer, and one set of APIs. SAM.gov, FPDS, FSRS, CPARS, eSRS, the opportunities feed, the exclusions service, and the wage determinations service all sit under the IAE umbrella. The Oct 6, 2026 cutover is the first time the data layer has actually been unified; until now, the systems talked to each other through nightly extracts, which is why a Saturday night change in one system did not show up in the others until Monday. The IAE replaces those extracts with a single source of truth, and the migration is the foundation for every later integration, including the planned Federal Procurement Data System rewrite and the FPDS-NG successor due in 2027.

What this page is not

This page is not a SAM.gov status page. It is not an IAE release note. It is not a substitute for reading the official IAE cutover communication your Entity Administrator received by email, and it is not legal advice on whether your representations are still accurate. ZeroGov is independent, not SAM.gov, and the IAE migration is exactly the kind of event where the official source should be your first read. Treat this page as a plain chronology and a sanity check, not as a system of record.

What to do this week, in order

Monday Oct 6, 2026, first hour online: log in, confirm the new dashboard, do not push a renewal yet, just read. Monday Oct 6, 2026, second hour online: open your entity record and compare against the Oct 4 export. Tuesday Oct 7, 2026: open the reps and certs block and resolve any soft warnings the new validation service raises. Wednesday Oct 8, 2026: search the exclusions list for your own UEI and your active subs. Thursday Oct 9, 2026: if you have a renewal in the next 60 days, queue the renewal now rather than waiting for the late October deadline window, because the throttle still favours the small one-off users. Friday Oct 10, 2026: write down the IAE case number for any ticket you opened, because the old SAM.gov ticket numbers do not all port cleanly.

For contractors who do not have an Entity Administrator, the order changes. Monday Oct 6, 2026: confirm your Login.gov account still works, because Login.gov is the only front door. Tuesday Oct 7, 2026: read the SAM.gov ticket tracker guide on ZeroGov, and file a ticket if the legacy host still serves you. Wednesday Oct 8, 2026: do not modify your record until the IAE has confirmed your case is closed, because a write during an open ticket can race the migration and produce a record that looks correct on the surface but fails the next validation pass.

Common traps in the first 72 hours

Trap one, the legacy URL. Contractors who bookmarked the old SAM.gov domain sometimes still see a cached page that does not reflect the new IAE data. The fix is simple, clear the cache and use the canonical domain, but the trap is that a cached page can mislead you into thinking the migration did not land when in fact the migration did land and your browser did not.

Trap two, the case tracker. SAM.gov tickets opened over the weekend show up in the new IAE case view, but the case numbers do not all carry the same prefix. If you only search for the old SAM prefix, you will miss the new IAE tickets. The IAE case view is the system of record now, and the SAM-only search is a legacy view.

Trap three, the soft warning on the reps block. The new validation service flags inconsistencies that the old SAM.gov form used to let through. The most common one is a small business set-aside flag set to yes while the size standard representation in 52.219-1 reads no, often because the contractor flipped from one NAICS to another without revisiting the size standard. The fix is to update the size standard representation to match the flag, not to silence the warning, because the warning is the validation doing its job.

Trap four, the banking addendum. The banking addendum is a re-entry, not a confirmation, and the new stack does not pre-fill the old addendum on the edit screen. Contractors who click through expecting the addendum to be already populated often save an empty addendum by accident. The fix is to open the addendum, confirm the routing and account numbers, and re-save.

Where this leaves the next 90 days

Wave two in late November 2026 will pull opportunity posting across, which is the cutover most small contractors will feel next, because contract opportunities is the daily use surface. Wave three in early December 2026 will pull FSRS and eSRS across, which is the cutover most prime contractors will feel, because subaward reporting has a December 31, 2026 deadline for FY2026 final reports. ZeroGov will track each cutover the same way, with a plain chronology and a sanity-check checklist, and will keep repeating the independent disclaimer on every page: ZeroGov is independent, not SAM.gov, not the IAE, not GSA, and not the IRS.

The IAE migration is the kind of structural change that pays off slowly. The first 30 days will look like outages and soft warnings. The next 60 days will look like a slower, more consistent system. The 90-day mark is where the data layer should start to feel boring, which is the highest compliment a federal procurement system ever earns.

Independent information, not legal advice. Confirm status and rules on sam.gov and the current FAR text.