NetApp Copy and Sync

Name: NetApp Copy and Sync
Brand: NetApp
Rating: 4.5 (10 reviews)

Leader

Making your data infrastructure more seamless, more dynamic, and higher performing than ever before.

Est 1992|Valuation $42.3B|Raised $6.6B

LinkedIn 782K|Website|Web traffic 856K|FTEs 11,700|HQ San Jose, California, US

MarketsData Integration (ETL/ELT)Desktop as a Service (DaaS)

Published Oct 24, 2026

01Common complaints

1. Backup and recovery is the primary requirement rather than sync. - For requirements that center on recoverable historical versions, immutability, or ransomware rollback, snapshot or backup tooling with versioned retention is the appropriate solution. Sync services can propagate deletions and encrypted data to targets. 2. Migration requires preservation of Windows ownership semantics end-to-end. - Copy and Sync may preserve ACLs in some scenarios, but it does not preserve file/folder ownership in SMB ACL copy operations; vendors recommend Windows-native tools such as robocopy when ownership must be preserved. 3. Workloads dominated by millions of very small files where pre-scan overhead is unacceptable. - Practitioner feedback indicates that many sync tools face operational challenges in extreme file-count workloads; this can present a project delivery risk. 4. The environment is exclusively AWS and an organization prefers a single-vendor AWS-native transfer service. - AWS DataSync may be operationally simpler for AWS-centric organizations. 5. The procurement process requires continuously updated, publicly verifiable compliance attestations for this specific service. - Vendor trust center materials indicate some services may not have continued public certification, so procurement should validate report scope and currency.

Deal disqualifiers (poor fit)

Primary requirement is backup, immutability, or versioned restore; sync is not sufficient by itself for these use cases.
Need to preserve SMB file/folder ownership automatically as part of the copy; vendor guidance points toward OS-level tools for ownership preservation.
Environments that cannot permit outbound Data Broker connectivity or cannot meet network prerequisites.

Vendor-documented / implied limitations

Data Broker requires outbound connectivity to the control plane.
SMB ownership is not preserved as part of SMB ACL copy operations; vendor guidance suggests alternate tools for ownership preservation.
SMB encryption: the service can copy already-encrypted SMB data but does not provide SMB-side encryption in all transfer paths.

Community-reported issues (anecdotal)

Slow transfers reported in some NFS scenarios with large datasets.
Skipped files reported in edge cases involving anomalous timestamps.

Roadmap / naming transitions

Copy and Sync has undergone branding transitions (Cloud Sync → BlueXP copy and sync → NetApp Copy and Sync). Confirm SKUs, support boundaries, and documentation versions in procurement to avoid ambiguity.

02Why they buy

Documented capabilities

Support for a broad range of source and target types (NFS, SMB, and multiple object stores) with a consistent sync-relationship model.
SaaS orchestration with an agent-based execution model (Data Broker) that can be deployed in major clouds or on-premises to perform payload transfer.

Claims requiring validation

Vendor and partner collateral sometimes include performance claims or comparative multipliers; procurement should request reproducible benchmarks and validate against representative datasets.

Competitor advantages

rclone: low cost and flexibility for teams comfortable with scripting.
AWS DataSync: closer integration with AWS endpoints and billing for AWS-centric organizations.
ONTAP SnapMirror: storage-native replication with ONTAP-to-ONTAP semantics when applicable.

03Field reports

Review platform reality check

Gartner Peer Insights pages are often access-restricted; a product-specific Copy and Sync review page was not available in the accessible dataset.
G2 lists Copy and Sync (BlueXP Copy and Sync) and contains review snippets; however, publicly visible snippets appear generic and do not always include practitioner role or environment details. These should not be weighted heavily without reviewer validation.

G2 review snippets (positive and negative)

Examples of publicly visible reviewer comments (paraphrased): - Some reviewers describe the product as convenient and note it can resume transfers after interruptions, indicating resume/retry behavior. - Other reviewers indicate the product "works well," and praise support and relative ease of implementation, while also noting areas for improvement without elaboration. Analyst note: Short review snippets frequently lack context (environment, dataset size, protocols used) and thus should be corroborated with verified references or direct customer conversations.

Community feedback — strengths and pain points

Practitioner forums and community discussions highlight several recurring themes: Performance concerns (very large datasets / throughput): - Reports exist of slow progress when copying very large directories in some scenarios, suggesting that tuning and appropriate broker sizing may be required for high-throughput migrations. Scale pain with very large file counts: - Many migration tools exhibit expensive pre-scan or metadata collection costs when dealing with extremely large file counts. This is a general migration challenge; Copy and Sync users have reported friction in extreme-scale scenarios. Edge cases / correctness (timestamp anomalies): - Anecdotal reports indicate that unusual timestamp conditions (for example, files with modification timestamps far in the future) can lead to unexpected behavior, such as skipped files. Ransomware/replication risk: - Because sync tools replicate live data, they can also propagate encrypted or deleted data. Organizations that require versioned recovery or immutability should use snapshots or backup systems in addition to sync. Substitution by DIY tooling: - In some object-to-object migrations, practitioners have reported using rclone successfully as a lower-cost or simpler alternative when advanced orchestration or scheduling is not required.

Why customers select Copy and Sync (inferred from sources)

Vendor materials describe the product as providing hybrid migration capabilities with a managed interface and support for multiple endpoints.
Vendor-published customer quotes highlight scenarios where migrations were completed without application changes and with integration to existing authentication systems in specific deployments.

Why some customers churn or avoid the product (inferred)

Common reasons indicated in community feedback and documentation:

Unexpected slowness for specific datasets or topologies.
Scale challenges with very large file counts.
Cost growth when modeling many sync relationships under per-relationship billing.
Sync is not a substitute for backup or immutable retention; this can be a business risk if not addressed architecturally.

Siemens Healthineers (vendor-published testimonial)

The vendor-published testimonial from Siemens Healthineers indicates Copy and Sync was used to migrate workloads to Cloud Volumes ONTAP without application changes while maintaining integration with AD/DNS. This is a vendor-published testimonial. Critical evaluation / gaps: - The publicly accessible excerpt is a testimonial without independently verifiable metrics (for example, migration duration, throughput, aggregate file quantities, failure rates, or costs). - Procurement should request the complete customer story, including quantitative metrics and environment details, and validate similarity to the buyer's intended migration scenario.

04Best fit

Company sizes

Typically mid-market to very large organizations operating multiple NAS or object endpoints.
Teams with dedicated storage or cloud infrastructure responsibilities.

Industries / verticals

Regulated or data-intensive industries such as healthcare, life sciences, manufacturing, media, and financial services, where hybrid data mobility is required. Regulated buyers must validate compliance attestations for the service explicitly.

Roles and personas

Storage administrators (ONTAP / NAS specialists)
Cloud infrastructure engineers
Data platform and analytics teams that require data locality
IT operations teams that manage migrations and cutovers

Pain points addressed

Moving data across protocols and storage types without developing custom pipelines.
Maintaining synchronization between source and destination during transition windows.
Central orchestration for multiple sync relationships.

Qualification criteria (good fit)

Requirement for scheduled delta synchronization after an initial copy.
Ability to validate data integrity (for example, through checksums or sample validation) and to handle permission semantics as required.
Capability to place and size Data Brokers appropriately close to relevant endpoints.

05The pitch

What the product does (core value proposition)

NetApp Copy and Sync (previously known as NetApp Cloud Sync, and renamed from "BlueXP copy and sync" to "NetApp Copy and Sync") is a SaaS-based data movement service that copies and periodically re-syncs (delta changes) file and object data between heterogeneous storage endpoints (on-premises and cloud). It is commonly used for: - Migration (one-time or staged cutovers) - Ongoing synchronization for hybrid workflows - Repatriation (cloud → on-prem) Operationally, a Data Broker (agent) runs in the customer cloud account or on-premises and communicates outbound to the service over HTTPS (port 443). The service orchestrates "sync relationships" and schedules. Vendor documentation provides configuration and operational details.

Target market and positioning

- Mid-market to enterprise IT teams that manage NAS and object storage across hybrid/multi-cloud environments. - Particularly relevant for organizations already using ONTAP, Cloud Volumes ONTAP, StorageGRID, or NetApp offerings hosted by hyperscalers. - Often selected when organizations want a guided, managed approach rather than building custom pipelines with tools such as rsync or rclone. It is not equivalent to storage-system-native replication for block-level or volume-level data when compared to ONTAP replication.

Get a comprehensive analysis of NetApp Copy and Sync including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 24, 2026

01Common complaints

Backup and recovery is the primary requirement rather than sync.
- For requirements that center on recoverable historical versions, immutability, or ransomware rollback, snapshot or backup tooling with versioned retention is the appropriate solution. Sync services can propagate deletions and encrypted data to targets.
Migration requires preservation of Windows ownership semantics end-to-end.
- Copy and Sync may preserve ACLs in some scenarios, but it does not preserve file/folder ownership in SMB ACL copy operations; vendors recommend Windows-native tools such as robocopy when ownership must be preserved.
Workloads dominated by millions of very small files where pre-scan overhead is unacceptable.
- Practitioner feedback indicates that many sync tools face operational challenges in extreme file-count workloads; this can present a project delivery risk.
The environment is exclusively AWS and an organization prefers a single-vendor AWS-native transfer service.
- AWS DataSync may be operationally simpler for AWS-centric organizations.
The procurement process requires continuously updated, publicly verifiable compliance attestations for this specific service.
- Vendor trust center materials indicate some services may not have continued public certification, so procurement should validate report scope and currency.

Deal disqualifiers (poor fit)

Primary requirement is backup, immutability, or versioned restore; sync is not sufficient by itself for these use cases.
Need to preserve SMB file/folder ownership automatically as part of the copy; vendor guidance points toward OS-level tools for ownership preservation.
Environments that cannot permit outbound Data Broker connectivity or cannot meet network prerequisites.

Vendor-documented / implied limitations

Data Broker requires outbound connectivity to the control plane.
SMB ownership is not preserved as part of SMB ACL copy operations; vendor guidance suggests alternate tools for ownership preservation.
SMB encryption: the service can copy already-encrypted SMB data but does not provide SMB-side encryption in all transfer paths.

Community-reported issues (anecdotal)

Slow transfers reported in some NFS scenarios with large datasets.
Skipped files reported in edge cases involving anomalous timestamps.

Roadmap / naming transitions

Copy and Sync has undergone branding transitions (Cloud Sync → BlueXP copy and sync → NetApp Copy and Sync). Confirm SKUs, support boundaries, and documentation versions in procurement to avoid ambiguity.

02Why they buy

Documented capabilities

Support for a broad range of source and target types (NFS, SMB, and multiple object stores) with a consistent sync-relationship model.
SaaS orchestration with an agent-based execution model (Data Broker) that can be deployed in major clouds or on-premises to perform payload transfer.

Claims requiring validation

Vendor and partner collateral sometimes include performance claims or comparative multipliers; procurement should request reproducible benchmarks and validate against representative datasets.

Competitor advantages

rclone: low cost and flexibility for teams comfortable with scripting.
AWS DataSync: closer integration with AWS endpoints and billing for AWS-centric organizations.
ONTAP SnapMirror: storage-native replication with ONTAP-to-ONTAP semantics when applicable.

03Field reports

Review platform reality check

Gartner Peer Insights pages are often access-restricted; a product-specific Copy and Sync review page was not available in the accessible dataset.
G2 lists Copy and Sync (BlueXP Copy and Sync) and contains review snippets; however, publicly visible snippets appear generic and do not always include practitioner role or environment details. These should not be weighted heavily without reviewer validation.

G2 review snippets (positive and negative)

Examples of publicly visible reviewer comments (paraphrased):

Some reviewers describe the product as convenient and note it can resume transfers after interruptions, indicating resume/retry behavior.
Other reviewers indicate the product "works well," and praise support and relative ease of implementation, while also noting areas for improvement without elaboration.

Analyst note: Short review snippets frequently lack context (environment, dataset size, protocols used) and thus should be corroborated with verified references or direct customer conversations.

Community feedback — strengths and pain points

Practitioner forums and community discussions highlight several recurring themes:

Performance concerns (very large datasets / throughput):

Reports exist of slow progress when copying very large directories in some scenarios, suggesting that tuning and appropriate broker sizing may be required for high-throughput migrations.

Scale pain with very large file counts:

Many migration tools exhibit expensive pre-scan or metadata collection costs when dealing with extremely large file counts. This is a general migration challenge; Copy and Sync users have reported friction in extreme-scale scenarios.

Edge cases / correctness (timestamp anomalies):

Anecdotal reports indicate that unusual timestamp conditions (for example, files with modification timestamps far in the future) can lead to unexpected behavior, such as skipped files.

Ransomware/replication risk:

Because sync tools replicate live data, they can also propagate encrypted or deleted data. Organizations that require versioned recovery or immutability should use snapshots or backup systems in addition to sync.

Substitution by DIY tooling:

In some object-to-object migrations, practitioners have reported using rclone successfully as a lower-cost or simpler alternative when advanced orchestration or scheduling is not required.

Why customers select Copy and Sync (inferred from sources)

Vendor materials describe the product as providing hybrid migration capabilities with a managed interface and support for multiple endpoints.
Vendor-published customer quotes highlight scenarios where migrations were completed without application changes and with integration to existing authentication systems in specific deployments.

Why some customers churn or avoid the product (inferred)

Common reasons indicated in community feedback and documentation:

Unexpected slowness for specific datasets or topologies.
Scale challenges with very large file counts.
Cost growth when modeling many sync relationships under per-relationship billing.
Sync is not a substitute for backup or immutable retention; this can be a business risk if not addressed architecturally.

Siemens Healthineers (vendor-published testimonial)

Critical evaluation / gaps:

The publicly accessible excerpt is a testimonial without independently verifiable metrics (for example, migration duration, throughput, aggregate file quantities, failure rates, or costs).
Procurement should request the complete customer story, including quantitative metrics and environment details, and validate similarity to the buyer's intended migration scenario.

04Best fit

Company sizes

Typically mid-market to very large organizations operating multiple NAS or object endpoints.
Teams with dedicated storage or cloud infrastructure responsibilities.

Industries / verticals

Regulated or data-intensive industries such as healthcare, life sciences, manufacturing, media, and financial services, where hybrid data mobility is required. Regulated buyers must validate compliance attestations for the service explicitly.

Roles and personas

Storage administrators (ONTAP / NAS specialists)
Cloud infrastructure engineers
Data platform and analytics teams that require data locality
IT operations teams that manage migrations and cutovers

Pain points addressed

Moving data across protocols and storage types without developing custom pipelines.
Maintaining synchronization between source and destination during transition windows.
Central orchestration for multiple sync relationships.

Qualification criteria (good fit)

Requirement for scheduled delta synchronization after an initial copy.
Ability to validate data integrity (for example, through checksums or sample validation) and to handle permission semantics as required.
Capability to place and size Data Brokers appropriately close to relevant endpoints.

05The pitch

What the product does (core value proposition)

Migration (one-time or staged cutovers)
Ongoing synchronization for hybrid workflows
Repatriation (cloud → on-prem)

Operationally, a Data Broker (agent) runs in the customer cloud account or on-premises and communicates outbound to the service over HTTPS (port 443). The service orchestrates "sync relationships" and schedules. Vendor documentation provides configuration and operational details.

Target market and positioning

Mid-market to enterprise IT teams that manage NAS and object storage across hybrid/multi-cloud environments.
Particularly relevant for organizations already using ONTAP, Cloud Volumes ONTAP, StorageGRID, or NetApp offerings hosted by hyperscalers.
Often selected when organizations want a guided, managed approach rather than building custom pipelines with tools such as rsync or rclone. It is not equivalent to storage-system-native replication for block-level or volume-level data when compared to ONTAP replication.

Get a comprehensive analysis of NetApp Copy and Sync including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →