Moving to a Different Team or Office Internally on H-1B: When You Need an Amendment and When You Don't

Moving to a different team or office on H-1B doesn't always require an amendment — but sometimes it does, and missing that line can put your status at risk.

Your manager just offered you a move to the platform engineering team — a great opportunity, lateral or slightly upward, same company, same office building. Or maybe the company is opening a new office in Austin and wants you to relocate while keeping your current title. Both feel routine. On paper they're internal moves. On paper, neither requires you to re-enter the H-1B lottery or go through the full sponsorship process again.

But depending on the specifics, one or both might require your employer to file an amended H-1B petition before you make the switch. Getting this wrong doesn't just create a paperwork headache — it can mean you're working outside your authorized status, which USCIS takes seriously and which can quietly create problems for your extension, your green card application, or your visa stamp renewal years down the road.

The good news is the analysis is not that complicated once you understand the two variables USCIS actually cares about: your work location and your job duties. Here is how to think through it.

The governing rule: what counts as a material change

USCIS does not require an amendment every time something changes in your employment. The threshold is whether the change is material — meaning, if USCIS had known about the change at the time of the original petition approval, it would have affected the outcome. The controlling precedent is Matter of Simeio Solutions, LLC (AAO 2015), which drew the line explicitly around worksites outside the original Labor Condition Application's geographic area.

The H-1B Modernization Rule (effective January 17, 2025) incorporated and reinforced this framework. The rule also codified deference to prior approvals — meaning that on extensions and amendments, USCIS officers must generally defer to the prior approval absent material error or new information. That deference protection only helps you, however, if you file correctly. If you skip a required amendment and then file an extension with the changed facts, the officer may find a discrepancy and that deference disappears.

Two categories drive almost every internal-move amendment analysis: worksite and duties/SOC code.

Location changes: the MSA test

Your H-1B is tied to a specific Labor Condition Application filed with the Department of Labor. That LCA certifies that your employer will pay you at least the prevailing wage for your role in a specific geographic area — technically, a Metropolitan Statistical Area (MSA).

If your new location falls within the same MSA as the current LCA, you generally do not need to file an amended I-129 with USCIS. However, your employer must:

• Post a new LCA notice at the new worksite for 10 consecutive business days, or
• Provide electronic notice to affected workers per DOL notice rules, and
• Maintain the new posting documentation in the Public Access File

If your new location is in a different MSA — including a different city, even if it's the same state — your employer must file a new LCA for that location AND file an amended I-129 petition with USCIS. The amendment must be approved before you begin working at the new location.

There is one exception worth knowing: the short-term placement rule (20 CFR §655.735). An H-1B worker may be placed at a non-LCA-covered location for up to 30 workdays per year (or up to 60 days if the worker's regular worksite is at a different location) without triggering a new LCA requirement. This is designed for travel and short project deployments — not for a permanent relocation. If the Austin move is permanent, the exception does not apply.

MSA examples

The remote work scenario deserves special attention. If you negotiate a remote arrangement where your home city is in a different MSA than the LCA-certified location, your employer should file an amended LCA and likely an amended petition. The return-to-office LCA worksite amendment guidance covers this intersection in detail.

Duty changes: the SOC code and wage-level test

The second category is more judgment-intensive. Moving to a different team is not automatically a material change — it depends on what the team actually does and whether the work you will perform differs materially from the work described in your approved I-129.

USCIS looks at two sub-questions:

1. Does the role still fall under the same Standard Occupational Classification (SOC) code? Your original petition specified a SOC code (for example, 15-1252 for Software Developers) and an associated job title. If the new role would require reclassification to a different SOC code (say, 11-3021 for Computer and Information Systems Managers), that is a material change.

2. Does the wage level change? LCAs specify a wage level (I through IV) based on complexity and supervision. If the new role's duties put you at a different prevailing-wage level — and your employer is still paying the old LCA wage, which is now below the prevailing wage for the new level — that is a material change. More on wage levels in the DOL prevailing wage levels guide.

Typical team moves that do not require an amendment:

• Moving from one product team to another, doing the same software engineering work
• Switching from backend to frontend on a different product, still coded as a Software Developer
• Lateral move to a different manager within the same department with unchanged duties
• Title change from "Software Engineer II" to "Software Engineer II – Platform" without SOC or duty change

Typical team moves that do require an amendment:

• Moving from individual contributor engineer to team lead or engineering manager, if the SOC code shifts to a management code
• Moving from software engineering to a product management role
• Moving from technical individual contributor to a business analyst or solutions architect role that uses a different SOC
• Significant duty expansion — for example, adding independent research and development responsibilities that change your wage level from II to III or IV

Duties change matrix

Promotion or title change: a related but distinct scenario

A promotion within the same specialty occupation — say, from Software Engineer to Senior Software Engineer — is typically not a material change requiring an amendment, unless the promotion comes with a wage-level bump. If the prevailing wage for the new title at the new level exceeds what the current LCA certified, your employer should file a new LCA and an amended petition. You cannot just pay above the LCA wage on a voluntary basis and call it compliant — the LCA must be updated to match the actual job.

The promotion and title-change LCA amendment guide covers this in more detail.

The filing process: what the amendment actually involves

When an amendment is required, the process is:

1. Employer files a new LCA with DOL for the new worksite or wage level. Standard LCA certification takes 7 calendar days.
2. LCA is posted at the new worksite (or electronically notified to workers) for 10 consecutive business days. This can overlap with the LCA certification window.
3. Employer files amended I-129 with USCIS, attaching the newly certified LCA, an updated support letter, and updated documentation of the changed role or location.
4. USCIS adjudicates. Standard processing: 3-6 months. Premium processing ($2,965, effective March 2026): 15 business days.
5. You start the new role after USCIS approves the amendment.

The key distinction from an inter-employer transfer: you cannot use AC21 portability to start the changed role on a receipt notice. The amendment must be approved before you work in the new capacity. This is because AC21 portability specifically applies to transfers to a new employer under 8 USC §1184(n), not to amendments within the same employer.

Practically, this means you need to plan for the amendment timeline before accepting the internal move. If your employer offers premium processing, use it — 15 business days is manageable. Standard processing on a 3-6 month horizon creates a problem if the team move is time-sensitive.

How to approach this conversation with your employer

Most internal teams assume that internal moves don't involve immigration. The manager who offered you the role may have no idea that a USCIS filing is needed before you switch. You'll need to flag it, and that means understanding your own situation well enough to explain it.

The key questions to bring to your employer's immigration team or outside immigration counsel:

• Is the new role in a different MSA than my current LCA?
• Does the new role use the same SOC code as my current petition?
• Will my wage level (I-IV) stay the same under the new role?
• What is the expected timeline if an amendment is needed?

Getting promoted or being asked to take on more is a good position to be in. The getting promoted as an international employee guide covers the career and internal-relationship side of this well. On the visa side, treat it as a pre-condition: confirm the amendment status before accepting an effective date, not after.

Special considerations for cap-exempt employers

If you work at a cap-exempt employer — a university, a nonprofit research organization, or a government research organization — the same material-change rules apply to amendments. Cap-exempt status does not exempt you from the requirement to file an amended petition when duties or worksite change materially. The advantage of cap-exempt employment is primarily that you avoided the lottery; it does not change the LCA and amendment compliance obligations. See the broader H-1B specialty-occupation modernization rule overview for the framework.

Impact on your green card process

If you have a PERM-based green card case in progress (EB-2 or EB-3), an unamended material change can create a problem at the I-140 or adjustment-of-status stage. USCIS compares the job you are actually doing against the job described in the approved I-129. If they don't match — because you changed roles without amending — an officer can find a discrepancy that undermines the bona fides of your petition.

If you're well into a PERM process and a team move comes up, tell your immigration attorney before accepting. In some cases the move can proceed cleanly. In others it may require restarting PERM for the new role — which can reset a priority date, a significant cost for workers from India or China where EB-2/EB-3 backlogs are long.

Common mistakes

Assuming that "same employer" means no filing is needed. It's the most common misconception. USCIS amended-petition requirements are entirely about whether the authorized role has changed, not about whether the company's name on your paycheck has changed.

Starting the new role before the amendment is approved. Unlike AC21 portability for transfers, amendments require approval before you work in the new capacity. This is an unauthorized-employment violation if you start early. The fact that your employer offered you the move in good faith does not cure the violation.

Relying on a verbal confirmation from HR instead of counsel. HR generalists often do not know the LCA and amendment rules. The question "do I need an amendment?" should go to immigration counsel, not to the HR coordinator who processed your onboarding.

Not accounting for amendment timing in the job-change negotiation. If a team move needs an amendment, your effective start date on the new team is roughly 15 business days (premium) to 3-6 months (standard) away. Factor that into the conversation with your manager, not after you've already agreed to a start date.

Forgetting the public access file. Even when a new LCA posting (rather than a full amendment) is all that's needed, the employer must update the Public Access File to include the new LCA and worksite documentation. Employers that neglect this expose themselves to DOL audit findings, which can indirectly affect your H-1B renewals.

Ignoring remote work as a worksite change. If you're moving to a different city for personal reasons and proposing remote work, and that city is outside your current LCA's MSA, that is a worksite change. The fact that you're at home — not in a company office — does not eliminate the LCA obligation. USCIS site visits (authorized and expanded under the H-1B Modernization Rule) now extend to home offices.

Frequently asked questions

Does moving to a different team within the same company require an H-1B amendment?

It depends on whether the change is material. If the move changes your job duties significantly, your job title in a way that shifts the occupational classification, or your prevailing wage level, USCIS considers it a material change requiring an amended I-129 and a new Labor Condition Application. A lateral move to a different team doing the same work at the same location usually does not.

Does moving to a different office location within the same employer require an H-1B amendment?

It depends on whether the new location falls within the same Metropolitan Statistical Area covered by your current Labor Condition Application. If the new office is in the same MSA, no amendment is required but you may need a new LCA posted at the worksite. If the new office is in a different MSA or a non-contiguous location, a new LCA and an amended I-129 are required before you start working there.

What counts as a material change to H-1B status under USCIS rules?

USCIS defines a material change as one that would have resulted in a denial of the original petition had USCIS known about it at the time of approval. This typically includes significant duty changes, a shift to a different SOC occupational code, a move to a different MSA worksite, or a wage-level change that misaligns with the certified LCA. Small title changes or minor responsibility shifts without SOC-code impact are generally not material.

Can I start the new role before the amendment is approved?

No. Unlike an H-1B transfer to a new employer (where AC21 portability lets you start on the receipt notice), an amendment for a material change within the same employer must be approved before you begin working in the changed role. Working in the new capacity before approval means you are working outside the scope of your authorized H-1B status.

What happens if I already started the new role without filing an amendment when one was required?

Working outside H-1B authorization is an unauthorized employment violation. It can affect your future H-1B extensions, green card applications, and visa stamp renewals. If you realize the oversight, consult an immigration attorney immediately about filing a late amendment with an explanation, and do not continue in the unauthorized role. The sooner you address it, the more options you have.

Internal moves are a normal part of a tech career. The H-1B rules around them are navigable once you know what the two triggers are: worksite MSA and material duty/SOC change. Most routine team moves do not require an amendment. Location changes across MSAs always do. Promotions with wage-level shifts typically do. The cost of getting it right is a conversation with your employer's immigration team before the effective date. The cost of getting it wrong can follow you through every future immigration filing.

If you are working through a specific internal move and not sure which category it falls into, F1Jobs can help you frame the right questions for your immigration attorney — and connect you with employers who have mature internal immigration processes so you're never navigating this alone.