1. Introduction

Data migration barriers are contractual, technical, economic, legal, or operational obstacles that make it difficult for customers to transfer their data from one digital platform, software provider, cloud service, financial service, or other data-dependent provider to another.

In competition law, data migration barriers become significant when they increase switching costs, weaken customer mobility, protect an incumbent's market position, or prevent competitors from entering or expanding. A firm with substantial market power may therefore be able to retain customers not because its service is objectively superior, but because customers face substantial costs or risks in extracting and transferring their accumulated data.

Data migration barriers are particularly important in:

• Cloud computing;
• SaaS and enterprise software;
• Digital banking and financial services;
• E-commerce;
• Social-media platforms;
• Healthcare databases;
• Advertising technology;
• Customer relationship management systems;
• Logistics platforms;
• Enterprise resource planning;
• AI and machine-learning services; and
• Digital identity ecosystems.

2. Meaning of Data Migration

Data migration means transferring data from one information system or service provider to another.

For example, a company using Provider A's CRM system may wish to move:

• customer records;
• transaction histories;
• invoices;
• communications;
• analytics;
• customer preferences;
• metadata;
• workflow information; and
• historical reports

to Provider B.

The migration may be technically possible but commercially difficult because the incumbent may use proprietary formats, restrictive APIs, contractual limitations, high extraction charges, or incompatible systems.

3. What Are Data Migration Barriers?

A data migration barrier exists where the practical ability to transfer data is significantly restricted or made costly.

Major categories

4. Competition-Law Significance

Data migration barriers are not automatically unlawful.

Competition law generally becomes concerned when several additional conditions exist:

1. The undertaking possesses substantial market power;
2. Customers are dependent upon its service;
3. Switching is commercially significant;
4. The barrier is capable of restricting competition;
5. Competitors cannot reasonably replicate the incumbent's advantages;
6. The conduct lacks adequate objective justification; and
7. The effect is exclusionary or otherwise harmful to competitive conditions.

Thus:

Data migration difficulty + market power + substantial switching costs + foreclosure effect = potential competition-law concern.

5. Data Migration Barriers and Switching Costs

The central economic concept is switching cost.

Suppose:

• Provider A charges ₹10 million annually;
• Provider B charges ₹8 million;
• migration from A to B costs ₹5 million;
• migration takes six months; and
• historical data may be lost during migration.

Even though B is cheaper, the customer may remain with A.

Consequently, the incumbent can obtain a form of customer lock-in.

Switching-cost mechanism

Incumbent platform

↓

Customer accumulates data

↓

Data becomes integrated with proprietary software

↓

Customer becomes dependent on historical data

↓

Migration becomes expensive

↓

Customer remains with incumbent

↓

Competitors find customer acquisition difficult

↓

Competitive pressure decreases

6. Data Migration Barriers as an Entry Barrier

A new competitor may technically be able to offer a superior service but still struggle to attract customers.

The reason is that customers may say:

"The new provider is better, but moving our existing data would be too expensive."

This creates an artificial entry barrier.

The competitor therefore faces two problems:

• attracting new customers; and
• overcoming the incumbent's accumulated data advantage.

Data migration barriers can therefore reinforce network effects and economies of scale.

7. Data Portability and Data Migration

Data portability is closely related but not identical to data migration.

Data portability

The customer has the ability to obtain and reuse its data.

Data migration

The practical process of transferring and integrating that data into another system.

A provider may technically satisfy portability requirements while still creating migration difficulties.

For example:

A platform allows customers to download a CSV file but refuses to provide API access, metadata, historical relationships, or machine-readable records.

Formal portability exists, but effective migration may remain difficult.

8. Data Migration Barriers and Abuse of Dominance

Where a dominant undertaking deliberately creates or maintains migration barriers, several theories of competition-law liability may arise.

A. Exclusionary abuse

The incumbent may make it difficult for rivals to acquire customers.

B. Refusal to provide access

The incumbent may refuse necessary technical interfaces or data-transfer facilities.

C. Interoperability restriction

The incumbent may prevent its system from interoperating with competing systems.

D. Tying and bundling

Data may be effectively locked into a larger proprietary ecosystem.

E. Discriminatory access

The incumbent may provide migration functionality to affiliated businesses while restricting competitors.

F. Unfair contractual conditions

Excessive migration charges or unreasonable export restrictions may reinforce market power.

9. Data Migration Barriers and Essential Facilities

In exceptional circumstances, migration-related data or infrastructure may raise an essential-facilities-type issue.

A claimant would generally need to establish matters such as:

1. The facility or resource is indispensable;
2. Effective competition cannot reasonably be replicated;
3. Access is necessary to compete;
4. Refusal is capable of eliminating effective competition; and
5. There is no adequate objective justification.

However, ordinary commercial inconvenience is not enough.

A competitor cannot automatically demand access merely because obtaining or recreating the relevant data would be expensive.

10. Important Case Laws

Case 1: Microsoft Corp. v Commission (Microsoft)

European Commission, 2004; General Court, 2007

Microsoft was found to have abused its dominant position in relation to interoperability information concerning work-group server operating systems.

Relevance to data migration

The case is important because it demonstrates the competition-law significance of interoperability information.

Where proprietary technical information prevents rival systems from functioning effectively with a dominant system, interoperability restrictions can reinforce market power.

Principle

Competition law can become concerned where a dominant undertaking controls technical information necessary for competitors to achieve effective interoperability.

Application to migration

A modern equivalent could arise where:

• a dominant SaaS provider controls proprietary interfaces;
• customers cannot transfer operational data effectively;
• competing software cannot interact with the incumbent's system; and
• the resulting incompatibility materially protects the incumbent.

11. Case 2: Bronner v Mediaprint

CJEU, Case C-7/97, 1998

The case concerned access to a newspaper-delivery network controlled by another undertaking.

The Court adopted a demanding approach to refusal-to-deal/essential-facility arguments.

Relevance

The case establishes that not every commercially important facility must be made available to competitors.

The facility must generally be indispensable, and duplication must not be realistically possible.

Data-migration application

A customer or competitor cannot automatically demand access to an incumbent's proprietary database merely because:

• migration is expensive;
• recreating the database is difficult; or
• the incumbent possesses substantial historical information.

The indispensability threshold remains important.

12. Case 3: IMS Health GmbH & Co. KG v NDC Health

CJEU, Joined Cases C-418/01, 2004

IMS Health concerned access to a pharmaceutical sales-data structure.

The Court considered circumstances in which refusal to license intellectual property could amount to abuse of dominance.

Relevance to data migration

The case is significant because it illustrates the relationship between:

• proprietary information;
• market power;
• interoperability/compatibility;
• access;
• downstream competition; and
• refusal to license.

Data-migration analogy

Where customer data is embedded in a proprietary structure, competition authorities may need to distinguish between:

legitimate proprietary rights

and

strategic restrictions designed to exclude competitors.

13. Case 4: Microsoft Corp. v United States

U.S. District Court for the District of Columbia, 2001

The Microsoft litigation examined Microsoft's conduct concerning operating systems, browsers, and interoperability.

The case addressed how control over an important technological platform could be used to disadvantage competing technologies.

Relevance to migration barriers

The broader competition-law lesson is that technical architecture can influence competitive conditions.

A dominant digital platform may use:

• proprietary interfaces;
• compatibility restrictions;
• technical defaults;
• software integration; or
• control over access

to make competing products less attractive.

Application

A data migration barrier can similarly operate as a technical foreclosure mechanism even where the incumbent does not expressly prohibit customers from leaving.

14. Case 5: Google Android

European Commission, Google Android decision, 2018

The European Commission found Google dominant in several markets associated with Android and identified several practices concerning the Android ecosystem.

Relevance to migration barriers

The case demonstrates the importance of ecosystem effects.

Digital users do not always purchase isolated products. They may use an interconnected ecosystem consisting of:

• operating systems;
• applications;
• accounts;
• search;
• cloud storage;
• payments;
• advertising; and
• other services.

The more deeply a customer's information becomes integrated into an ecosystem, the more difficult switching can become.

Data-migration implication

Competition analysis may therefore consider whether technical integration produces ecosystem-level switching costs that make rival entry substantially more difficult.

15. Case 6: Google Shopping

European Commission, 2017; General Court, 2021

The Google Shopping proceedings concerned Google's treatment of competing comparison-shopping services in search results.

Relevance

The case illustrates the importance of data, platform architecture, visibility, and access to digital infrastructure in competition.

Although the case was not principally a data-migration case, it is relevant by analogy because digital competition frequently depends upon control over a platform's technical environment.

Migration relevance

A platform can make switching difficult not only through explicit contractual restrictions but also through:

• technical design;
• integration;
• ranking;
• interoperability restrictions; and
• control of complementary services.

16. Case 7: Salesforce/Slack

Salesforce's acquisition of Slack — European Commission, 2021

The Commission examined Salesforce's acquisition of Slack.

The transaction was reviewed in the context of competition in enterprise software and workplace collaboration.

Relevance to data migration

Enterprise customers often accumulate large quantities of:

• messages;
• files;
• workflow data;
• customer information;
• integrations;
• application histories; and
• organizational metadata.

These accumulated datasets can make switching between enterprise platforms costly.

Competition significance

In enterprise software mergers, authorities may therefore examine whether the combined company could increase:

• interoperability restrictions;
• switching costs;
• data portability barriers; or
• ecosystem dependence.

17. Case 8: Meta/Facebook and Data-Related Competition Concerns

Competition authorities have examined Facebook/Meta's use of data and the relationship between data advantages and market power in several proceedings.

The important competition-law concept is that a dominant digital platform can accumulate large quantities of user and business data, potentially reinforcing its competitive position.

Data-migration relevance

Migration barriers may become particularly important where customers or users have accumulated:

• social graphs;
• contact lists;
• behavioral histories;
• content;
• advertising information;
• business pages; and
• interaction histories.

The inability to transfer these elements effectively can increase multi-homing costs and switching costs.

18. Case 9: Qualcomm

European Commission / EU competition proceedings concerning Qualcomm

The Qualcomm proceedings illustrate the broader competition-law significance of exclusionary conduct in technology markets where technological ecosystems and customer relationships can create substantial switching costs.

Relevance

In technology markets, competition authorities may consider whether commercial arrangements make it difficult for customers to shift to rival suppliers.

Data migration barriers can operate in a similar manner when the customer's accumulated information becomes intertwined with the incumbent's technological ecosystem.

19. Case 10: Apple App Store / Digital-Ecosystem Proceedings

Various competition authorities have examined Apple's ecosystem and restrictions affecting developers and competing digital services.

Relevance to migration

The broader issue is whether a platform owner can use control over:

• APIs;
• technical interfaces;
• account systems;
• payment systems;
• application distribution; and
• interoperability

to make switching or multi-homing more difficult.

This is especially important when customer data is not merely stored on a platform but becomes functionally dependent on the platform's architecture.

20. Data Migration Barriers and Refusal to Deal

A particularly difficult legal issue is whether a dominant company has a duty to assist migration.

There is an important distinction:

Legitimate position

"We will provide our customers with their data in a commercially reasonable format."

versus

Potentially problematic position

"Customers may leave, but we will prevent them from extracting their historical data, metadata, or necessary technical information."

The second situation can produce significant competitive effects.

However, competition law does not generally impose a universal obligation upon every business to provide all proprietary information to rivals.

21. Excessive Migration Charges

A provider might permit migration but charge extremely high fees.

For example:

• basic export: ₹10,000;
• complete database export: ₹20 lakh;
• API access: ₹5 lakh per month;
• historical records: additional charge;
• metadata extraction: prohibited.

Such charges can have an exclusionary effect where customers are effectively economically prevented from switching.

The legal assessment would depend upon:

• the provider's market position;
• cost justification;
• contractual circumstances;
• level of the charge;
• availability of alternatives; and
• competitive effects.

22. Proprietary Data Formats

Another important barrier is the use of proprietary formats.

Suppose Provider A stores customer information as:

Proprietary database + proprietary metadata + proprietary relationships.

The customer receives only:

PDF/CSV export.

The information is technically "exportable," but the customer cannot reproduce the functionality of the original database.

This produces functional portability failure.

23. API Restrictions

APIs are particularly important in modern competition law.

An API can allow:

• automated data extraction;
• real-time synchronization;
• migration;
• interoperability;
• integration with third-party applications.

Restricting API access can therefore increase migration costs.

A competition authority may ask:

1. Is the API technically necessary?
2. Is the undertaking dominant?
3. Are competitors denied comparable access?
4. Is access available to affiliated businesses?
5. Are restrictions objectively justified?
6. Does the restriction materially reduce competition?

24. Data Migration and Cloud Computing

Cloud services provide a particularly important example.

A company may store:

• databases;
• applications;
• employee information;
• financial records;
• customer information;
• machine-learning models; and
• operational logs

with one cloud provider.

Migration may require:

• rewriting applications;
• changing APIs;
• transferring large volumes of data;
• reconstructing security configurations;
• changing databases;
• retraining employees; and
• redesigning workflows.

Consequently, cloud switching costs can become substantial even where formal data portability exists.

25. Data Migration and SaaS Lock-In

SaaS platforms can create lock-in through:

1. Proprietary formats

Data cannot easily be imported elsewhere.

2. Proprietary workflows

Business processes depend upon the incumbent's system.

3. API dependence

Third-party applications are built around the incumbent's API.

4. Historical-data dependence

Years of records remain inside the platform.

5. Metadata dependence

Relationships between records cannot be exported.

6. Integration dependence

CRM, accounting, HR and logistics systems become interconnected.

The resulting lock-in can be more powerful than a simple contractual prohibition on switching.

26. Data Migration Barriers in Mergers

Data migration issues can also arise in merger control.

Consider:

Company A + Company B

If the merged firm controls:

• customer databases;
• transaction histories;
• behavioral data;
• proprietary APIs; and
• interoperability infrastructure,

the merger may increase the ability to impose migration barriers.

Competition authorities may therefore examine whether the transaction will:

• increase switching costs;
• eliminate an alternative provider;
• consolidate valuable datasets;
• reduce interoperability;
• increase data concentration; or
• strengthen ecosystem effects.

27. Data Migration Barriers and Network Effects

Network effects can amplify migration barriers.

For example:

More users

↓

More data

↓

Better service

↓

More customers

↓

More data

↓

Greater ecosystem attractiveness

↓

Higher switching costs

This can produce a self-reinforcing competitive advantage.

A migration barrier may therefore have effects extending beyond individual customers.

28. Data Migration and Consumer Welfare

Data migration barriers can affect consumers through:

• higher prices;
• reduced choice;
• lower innovation;
• reduced privacy competition;
• inferior service quality;
• reduced interoperability; and
• weaker competitive pressure.

In zero-price digital markets, the relevant harm may not be monetary.

Instead, the concern may involve:

quality + privacy + innovation + choice + switching freedom.

29. Objective Justifications

Not every migration restriction is anticompetitive.

A provider may legitimately restrict or regulate migration because of:

Security

Preventing unauthorized extraction of sensitive information.

Privacy

Protecting personal data.

Cybersecurity

Preventing malicious bulk downloads.

Legal obligations

Compliance with statutory retention requirements.

Intellectual property

Protecting proprietary software or databases.

Technical limitations

Genuine infrastructure limitations.

Fraud prevention

Preventing abusive transfers.

The competition-law question is therefore whether the restriction is necessary and proportionate to a legitimate objective.

30. Data Migration Barriers and Privacy

Competition and privacy law increasingly overlap.

A provider may argue:

"We cannot transfer this data because it contains third-party personal information."

That may be legitimate in certain circumstances.

But privacy cannot necessarily be used as a blanket justification for every migration restriction.

A competition authority may ask whether the provider could achieve the same objective through:

• anonymisation;
• consent mechanisms;
• filtering;
• authentication;
• encryption; or
• controlled API access.

31. Evidence Used to Prove Data Migration Barriers

Competition authorities may examine:

• customer complaints;
• internal emails;
• migration costs;
• termination statistics;
• API documentation;
• contracts;
• technical architecture;
• export functionality;
• customer surveys;
• churn rates;
• internal pricing documents;
• engineering documents;
• interoperability tests;
• switching-time estimates; and
• evidence concerning competitor entry.

32. Economic Analysis

A useful economic framework is:

Effective switching cost

ESC = Financial Migration Cost + Time Cost + Data-Loss Risk + Integration Cost + Training Cost

If ESC is high relative to the expected benefit of switching, customers are unlikely to migrate.

For competition analysis, authorities may also examine:

• customer churn;
• elasticity of demand;
• multi-homing;
• market shares;
• entry barriers;
• interoperability;
• availability of substitutes; and
• counterfactual migration costs.

33. Difference Between Natural and Strategic Migration Barriers

Competition law is particularly concerned with the second category when undertaken by a dominant firm and capable of harming competition.

34. Key Legal Principles From the Cases

The cases collectively demonstrate several important principles:

Principle 1 — Interoperability matters

Microsoft demonstrates the competition significance of interoperability information.

Principle 2 — Indispensability is a high threshold

Bronner shows that refusal-of-access claims require more than ordinary commercial difficulty.

Principle 3 — Proprietary structures can have competitive significance

IMS Health illustrates the interaction between intellectual property, access, and competition.

Principle 4 — Digital ecosystems can reinforce market power

Google Android illustrates the importance of ecosystem architecture.

Principle 5 — Platform design can affect competition

Google Shopping demonstrates how technical and platform-related mechanisms can influence competitive conditions.

Principle 6 — Enterprise software markets require attention to switching and interoperability

The Salesforce/Slack investigation illustrates the relevance of ecosystem effects in enterprise collaboration markets.

35. Regulatory Remedies

Where data migration barriers are found to harm competition, possible remedies include:

1. Data portability

Require customers to obtain their data in usable formats.

2. API access

Require reasonable technical access for migration.

3. Interoperability

Require compatibility between competing services.

4. Prohibition of excessive fees

Prevent unreasonable migration charges.

5. Standardised formats

Require machine-readable formats.

6. Metadata portability

Permit transfer of associated metadata and relationships.

7. Migration assistance

Require reasonable technical assistance.

8. Non-discrimination

Prevent preferential migration treatment for affiliated entities.

9. Contractual reform

Remove contractual provisions unnecessarily restricting migration.

10. Structural remedies

In exceptional merger or dominance cases, stronger structural remedies may be considered.

36. Practical Example

Assume CloudCo has 75% of a relevant enterprise-cloud market.

A customer has stored ten years of:

• customer records;
• financial data;
• AI models;
• application data;
• metadata;
• audit logs.

CloudCo permits customers to download basic records but:

• refuses API access;
• charges enormous extraction fees;
• prevents metadata export;
• uses proprietary formats;
• requires six months for complete migration.

A rival offers a cheaper and technically superior service.

However, customers do not switch because migration would be prohibitively expensive.

Competition-law concerns

The authority would examine:

1. CloudCo's market position;
2. the actual availability of alternatives;
3. whether the data is indispensable;
4. migration costs;
5. whether restrictions are objectively justified;
6. whether competitors are foreclosed;
7. whether the conduct is discriminatory; and
8. whether less restrictive migration mechanisms are available.

The existence of these facts would not by itself establish an infringement; the legal and economic context would determine the outcome.

37. Compliance Measures for Businesses

Businesses operating digital platforms should consider:

• clear data-export policies;
• machine-readable formats;
• reasonable API access;
• transparent migration fees;
• interoperability standards;
• adequate security controls;
• privacy-compliant migration;
• reasonable transition periods;
• metadata portability;
• contractual review; and
• non-discriminatory access to migration tools.

Internal competition-law compliance should specifically identify whether technical teams are intentionally making migration difficult for customers.

38. Conclusion

Data migration barriers are an important modern competition-law issue because control over customer data can create substantial switching costs and reinforce digital market power.

The principal concern is not simply that migration is inconvenient. The relevant question is whether a firm—particularly a dominant undertaking—is using technical, contractual, economic, or ecosystem-based restrictions to make switching substantially more difficult and thereby weaken competitive pressure.

The leading principles from Microsoft, Bronner, IMS Health, Microsoft (US), Google Android, Google Shopping, and the Salesforce/Slack investigation demonstrate the broader legal framework involving interoperability, access, indispensability, ecosystem effects, switching costs, and digital-platform competition.