On June 3, 2026, U.S. Customs and Border Protection (CBP) released Cross-Border Service Import Compliance Guidance (V2.1), adding a new Section 4.7 for service imports involving data-bearing operations such as IT equipment relocation, server decommissioning, and data center moves. For customs filing, a signed Data Processing Security Declaration must now be submitted, covering data erasure methods, media disposal procedures, and third-party audit commitments. This update is particularly relevant for cross-border IT relocation services, data center migration projects, customs compliance teams, and supply chain service providers because it directly affects documentation readiness and service import compliance workflows.

Event Overview

According to the disclosed information, CBP published Cross-Border Service Import Compliance Guidance (V2.1) on June 3, 2026. The newly added Section 4.7 applies to service imports that involve operations on data carriers, including IT equipment migration, server takedown, and data center relocation.

The public update states that, together with customs declaration documents, companies must submit a signed Data Processing Security Declaration. The declaration must specify three core items: the method of data erasure, the process for media disposal, and a commitment to third-party audit.

At present, the confirmed information is limited to the release of the updated guidance and the newly added declaration requirement for relevant service import scenarios.

Which Industry Segments Are Affected

Cross-border IT relocation and data center migration service providers

These providers are the most directly affected because the updated rule explicitly covers IT equipment migration, server decommissioning, and data center relocation. The immediate impact lies in project documentation, service scope definition, and execution evidence. Analysis shows that service providers may need to align operational procedures more closely with customs filing requirements when projects involve data-bearing equipment or storage media.

The practical effect is not only on-site execution, but also on how relocation plans are documented before filing. If a service package previously emphasized logistics, dismantling, transport, and reinstallation, the update means data handling description now becomes a visible compliance element tied to import service paperwork.

Enterprises importing relocation-related services

Companies that purchase cross-border relocation, decommissioning, or migration services may also be affected because the customs submission requirement is attached to the service import process. From an industry perspective, buyers can no longer view technical migration and customs compliance as separate tracks when the project includes servers, storage devices, or other data-bearing assets.

The impact is likely to appear in vendor selection, internal approval flow, and filing preparation. A relocation provider that cannot clearly explain data erasure, media disposal, or audit commitment may create uncertainty for the importing enterprise during customs document assembly.

Customs compliance, trade compliance, and legal operations teams

These functions are affected because the update adds a new documentation expectation to relevant service import cases. Observably, compliance teams may need to determine more precisely whether a project falls within the data-carrier operation scope described by the guidance.

The main impact is on document review standards and interdepartmental coordination. Compliance personnel may need clearer internal checks to confirm whether the signed declaration is complete, whether wording on data treatment is consistent with project execution, and whether audit commitments are reflected in contractual materials.

Supply chain and project management service intermediaries

Supply chain coordinators, relocation project managers, and third-party implementation partners may be affected because they often bridge operational delivery and documentary submission. Current attention should focus on the fact that project schedules may become more dependent on pre-arranged compliance inputs when customs documentation must include a signed security declaration.

The impact may show up in milestone planning, handoff procedures, and responsibility allocation. If operational teams treat data handling details as a late-stage issue, filing readiness may be delayed even when transport or decommissioning work is otherwise ready.

What Companies and Practitioners Should Watch and How to Respond

Review whether existing project templates cover the new declaration requirement

Companies involved in IT relocation, server decommissioning, or facility migration should examine whether their current statements of work, customs filing checklists, and project templates already include the three disclosed elements: data erasure method, media disposal process, and third-party audit commitment. Analysis shows that missing these items at template level could create avoidable delays when a filing is prepared.

Clarify document ownership between technical teams and compliance teams

More suitable to understand this update as a documentation coordination issue as much as a technical one. Enterprises should identify who drafts the Data Processing Security Declaration, who verifies the technical description, and who ensures consistency with customs filing materials. Without this division of responsibility, the same project may carry different descriptions across operational and compliance documents.

Check whether service vendors can provide signed and auditable statements

From an industry perspective, this update makes vendor documentation capability more important in affected service imports. Buyers and project owners should confirm early whether providers can issue a signed declaration and whether they are prepared to describe erasure methods, media disposal flows, and audit commitments in a way that supports filing. This is especially relevant before project launch rather than at final submission stage.

Track further official wording and practical enforcement signals

Current attention should focus on the distinction between a published compliance requirement and its operational interpretation in specific cases. Companies should continue monitoring any further official clarification on scope, filing expectations, or supporting document standards. For now, a prudent response is to prepare around the confirmed text rather than assume broader or narrower application without additional official language.

Editor’s View / Industry Observation

Observably, this update indicates that for certain cross-border imported services, CBP is placing clearer emphasis on how data-bearing assets are handled within relocation and decommissioning work. It is more suitable to understand this not as a general expansion to all services, but as a targeted compliance signal for projects where physical equipment movement and data treatment intersect.

Analysis shows that the immediate result is documentary, not necessarily a confirmed change to every operational process in the market. However, the industry significance lies in the fact that data handling language is now explicitly linked to customs filing in the disclosed scenarios. That changes the level of attention companies should give to pre-filing preparation and vendor coordination.

From an industry perspective, this is both a concrete compliance requirement in the stated service categories and a signal that cross-border service imports involving data carriers may face closer scrutiny in documentation terms. That is why affected sectors should keep watching how the guidance is applied in practice.

In summary, the June 3, 2026 CBP guidance update matters because it adds a defined data security declaration requirement to service imports involving IT equipment relocation, server takedown, and data center moves. For industry participants, the key significance is not only the policy text itself, but the operational need to connect technical data handling, service contracting, and customs filing into one consistent compliance process. At this stage, it is more suitable to understand the update as a clear compliance signal with immediate documentation implications, while continued observation is still needed on how it will be applied in day-to-day business cases.

Source Information

Main source: U.S. Customs and Border Protection (CBP), Cross-Border Service Import Compliance Guidance (V2.1), released on June 3, 2026.

Items requiring continued observation: any subsequent official clarification on scope, document interpretation, or practical filing application related to Section 4.7.