ZenWeb - Blog - Data Portability Under PDPA: What It Means for Your CRM

Data Portability Under PDPA: What It Means for Your CRM

November 2, 2026

Share this post:

Data Portability Under PDPA: What It Means for Your CRM
TL;DR: Since 1 June 2025, section 43A of the PDPA lets a customer ask you to send their personal data directly to another business they choose. The request must be in writing by electronic means, and it applies only where transfer is technically feasible and formats are compatible. As at October 2026, the deadline, fees and data scope are still not prescribed, so get your CRM export-ready now.

Your CRM holds more than names and phone numbers. It holds every form a lead filled in, every order, every WhatsApp follow-up and every note your sales team typed. Under the new data portability right, a customer can ask you to hand part of that record to another business.

This guide explains data portability under PDPA in plain terms: what the law says, which CRM data is likely covered, what is still pending, and how to prepare your website and CRM. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients. We build the websites and lead systems; we are not lawyers. Rules are stated as at October 2026.

This post is general information, not legal or tax advice. Please confirm how the PDPA applies to your business with a licensed lawyer.

Can your CRM export one customer’s record cleanly?

If the answer is “we’d have to copy it by hand”, your system needs work before the rules are finalised. See ZenWeb’s web development services →

For a broader view of the 2024 amendments that created this right, this recorded webinar from a Malaysian university research centre is a helpful primer.

Key Amendments to Malaysia's Personal Data Protection Act 2010

Source video: Centre of Research for Cyber Security and Network on YouTube. Recorded in August 2024, before the amendments came into force; check dates against the official sources below.

1. What Is Data Portability Under the PDPA?

Quick Answer: Data portability under the PDPA is a customer’s right to ask a data controller to transmit their personal data directly to another data controller of their choice. The customer must give written notice by electronic means. The right is subject to technical feasibility and compatibility of the data format, and the controller must finish within a period still to be prescribed.

The right sits in the new section 43A, inserted by section 9 of the Personal Data Protection (Amendment) Act 2024 (Act A1727). Three points matter most for an SME:

  • It goes business to business. The data is sent to the other data controller directly, not handed to the customer as a file.
  • It must be asked for in writing, electronically. An email or a web form counts; a phone call does not.
  • It has a built-in limit. If a transfer is not technically feasible or the formats do not match, the request is limited by law.

This post covers what the right means for the data in your CRM. How you secure that system day to day is a separate topic, covered in our guide to PDPA security for web systems.

Key takeaway: Portability is about moving a customer’s record to someone else on their instruction. If your data lives in scattered spreadsheets and chat apps, you will struggle to do that safely.

2. When Did the Right Start, and What Is Still Pending?

Quick Answer: Section 43A came into force on 1 June 2025 in the third phase of the amendments. But the regulations and guideline that set the deadline, fees, data scope and technical standards were only proposed in a 2024 consultation paper. As at October 2026, the Commissioner’s website still lists data portability as a consultation paper, not a final guideline.

The Commissioner’s Public Consultation Paper No. 03/2024 sets out what the future rules may look like. Treat its proposals as direction, not law.

Data portability under PDPA: what is in force and what is still proposed, as at October 2026
Time-series table showing the stages of Malaysia’s data portability right from the 2024 consultation to October 2026, with the status of the statutory right, the deadline, fees, data scope and technical standards.
DateMilestoneStatus
2024Consultation Paper 03/2024 proposes regulations and a guidelineProposal only
17 Oct 2024Act A1727 published, inserting s.43ALaw passed, not yet in force
1 Jun 2025s.43A comes into force with DPO and breach notification rulesIn force
Oct 2026Deadline, fee cap, data whitelist and technical standardsNot yet prescribed

Source: Act A1727, its commencement order and Consultation Paper 03/2024, compiled by ZenWeb. As at October 2026. Licence.

The proposed deadline is 21 days, plus up to 14 more days if you cannot finish in time. That matches the access-request timing in section 31 of the Personal Data Protection Act 2010, so it is a sensible planning target. The paper also proposes a capped fee to cover costs, with no profit allowed. For the wider rule set, our PDPA compliance checklist for Malaysian marketers is the place to start.

Key takeaway: The right exists, but the detailed rules do not yet. Plan to answer within 21 days and recheck the Commissioner’s website before you rely on any detail.

3. Which CRM Data Would Be Covered?

Quick Answer: The consultation paper proposes covering only data the customer gave you directly, held electronically, and processed on consent or a contract. Data you work out yourself, such as lead scores or ad-interest segments, would be excluded. Observed data such as browsing history is still an open question in the paper.

Here is how typical CRM and website fields map to that proposal. The final whitelist may differ by industry.

Likely portability status of common CRM fields under the proposed scope
Data table mapping seven common CRM and website data fields held by Malaysian SMEs to their data type under Consultation Paper 03/2024 and their likely portability status.
CRM fieldData typeLikely status
Name, email, phone from your enquiry formProvided directlyLikely covered
Delivery address and order detailsProvided under a contractLikely covered
Member profile and marketing preferencesProvided directlyLikely covered
Pages viewed and session recordingsObservedOpen question
Lead score and sales stageDerivedLikely excluded
Ad-interest segment or audience tagInferredLikely excluded
Paper forms never keyed into a systemManual recordsLikely excluded

Source: ZenWeb mapping of paragraph 2.10 of Consultation Paper 03/2024. Proposals, not final rules. As at October 2026. Licence.

A few CRM situations need extra thought:

Key takeaway: Tag each CRM field as “provided”, “observed” or “derived” now. When the whitelist arrives, you will only need to adjust labels, not rebuild your system.

4. Portability vs Access vs Withdrawal Requests: What’s the Difference?

Quick Answer: An access request gives the customer a copy of their data. A correction request fixes wrong data. A withdrawal of consent makes you stop processing. A portability request moves the data to another business. Each has its own section, timing and handling, so your team needs to tell them apart.

Customers rarely use the legal names. “Please send my details to my new clinic” is a portability request; “What do you hold about me?” is an access request.

Four PDPA customer requests a Malaysian SME’s CRM must handle
Grouped comparison table of four PDPA data subject requests, access, correction, withdrawal of consent and data portability, showing the section, who receives the data, and the time limit for each.
RequestPDPA sectionData goes toTime limit
Accesss.30–31The customer21 days, plus 14 if you notify a delay
Corrections.34–35The customer (corrected copy)21 days
Withdraw consents.38Nobody; you stop processingOn receiving the notice
Portabilitys.43AAnother data controllerTo be prescribed (21 + 14 days proposed)

Source: Act 709 as amended by Act A1727, compiled by ZenWeb. As at October 2026. Licence.

Note what is missing: the PDPA has no standalone “right to be deleted”. Deletion usually follows from withdrawal of consent and the Retention Principle. Our guide to data access and deletion requests walks through those steps, and how long you can keep leads under PDPA explains when old records should go anyway. A portability request does not by itself require you to delete anything.

Key takeaway: Give staff one simple rule: if the customer names another business to receive their data, log it as a portability request and start the clock.

5. How Ready Is Your CRM for Data Portability?

Quick Answer: Readiness depends on whether you can pull one person’s record into a structured, machine-readable file such as CSV or JSON, quickly and securely. A CRM with per-contact export or an API is in good shape. Data split across spreadsheets, WhatsApp chats and email inboxes is the hardest to move.

The consultation paper notes that other countries expect a structured, commonly used, machine-readable format and mentions open formats such as XML, JSON and CSV. This illustrative scenario scores common SME setups against that expectation.

Illustrative scenario: data portability readiness of common SME setups (score out of 10)
Bar chart table scoring, in an illustrative scenario, how ready five common Malaysian SME customer-data setups are to export one person’s record in a structured machine-readable format, with the main gap for each.
SetupReadiness scoreMain gap
WhatsApp chats and email only2

No single record; manual copying
Shared spreadsheets4

Duplicates across tabs; weak access control
Website form plugin storing entries5

Entries not linked to orders or chats
Off-the-shelf CRM with contact export7

Export may mix provided and derived fields
Integrated CRM with API and field tags9

Needs a secure, logged transfer step

Source: Illustrative scenario by ZenWeb, based on the format expectations in Consultation Paper 03/2024. Scores are judgement-based, not measured data or a legal standard. As at October 2026. Licence.

Moving up the scale usually means joining form, order and chat data into one record. Our best CRM software for Malaysian SMEs roundup compares ready-made options, and custom CRM development cost covers the build route. If your CRM numbers already disagree with your analytics, fix that first; see GA4 data not matching your CRM.

Key takeaway: The law excuses transfers that are not technically feasible, but that is a poor plan. A clean one-record export also speeds up access requests and audits.

Leads stuck in forms, sheets and chats?

We connect website forms, orders and WhatsApp enquiries into one exportable customer record with role-based access. Plan a CRM-ready website build with ZenWeb →


6. Worked Example: A Customer Asks You to Send Their Data Elsewhere

Quick Answer: Confirm the request is in writing and from the real customer, pull only the fields that are likely covered, check the receiving business can accept the format, transfer it securely, and record what you sent and when. Aim to finish within 21 days while the official deadline is still pending.

Imagine a tuition centre member emails asking you to send their profile and payment history to a new centre’s system. This is an illustrative scenario, but each step follows section 43A and the consultation paper:

  1. Log the request. Note the date received; it was made by email, which meets the “electronic means” rule.
  2. Verify identity. Reply to the email address already on file, not a new one, before releasing anything.
  3. Confirm the receiver. Get the receiving business’s name and a named contact or upload point.
  4. Select the data. Export provided and contract data; leave out lead scores and internal notes.
  5. Check feasibility. Agree a format, such as CSV, that the receiver can read. If no workable method exists, explain why in writing.
  6. Transfer securely. Use an encrypted link or password-protected file, never an open attachment, and never include card numbers.
  7. Record and confirm. Keep a log of fields sent, method and date, and tell the customer it is done.

A wrong recipient is a data breach, so read data breach notification in Malaysia before you send. If the receiver stores data abroad, that is their transfer to manage; the rules for your own overseas tools are in using overseas CRMs under PDPA. Card numbers should never be in the file, and our guide to PCI DSS for small online stores explains why they should not sit in your CRM at all.

Key takeaway: Verifying the customer and the receiver is the step most often skipped. A fast transfer to the wrong place is worse than a careful one on day 20.

7. Data Portability PDPA Checklist for Your Website and CRM

Quick Answer: Map where customer data lives, tag each field by type, make sure one record can be exported in CSV or JSON, add a request channel to your website, brief staff, line up your vendors, and keep a request log. Then recheck the Commissioner’s site for the final regulations.

Work through these seven steps with whoever manages your website and CRM:

  1. Map your data. List every place customer data sits: forms, CRM, e-commerce, email tool, WhatsApp, spreadsheets.
  2. Tag each field. Mark it provided, observed or derived, using the table in section 3.
  3. Test a one-record export. Pull one test customer into CSV or JSON and time how long it takes.
  4. Add a request channel. A privacy-request form or email address on your privacy notice page gives you the written, electronic request the law expects.
  5. Brief your team. Show staff how to spot portability, access and withdrawal requests.
  6. Line up your vendors. Your CRM provider and agency should help with requests under their contract; see data processor duties for your agency.
  7. Keep a log. Record each request, the fields sent, the method and the date finished.

Two related risks often appear during this review. If you use AI tools to score or summarise leads, read AI and PDPA for Malaysian marketers. If your site handles larger volumes or critical services, check whether the Cyber Security Act 2024 applies to your website.

Key takeaway: Steps 3 and 4 do most of the work. If you can export one record cleanly and customers know where to ask, you are ahead of most SMEs.

8. Conclusion: Build for Portability Before the Rules Land

Data portability under PDPA is already law, but as at October 2026 the deadline, fee cap and data whitelist are still waiting on regulations. That gap is a chance to prepare calmly:

  • The right: section 43A needs a written electronic request and a direct transfer to another controller, where technically feasible.
  • Your data: what customers typed into your forms is the likely core, while lead scores and segments are likely out.
  • Your system: a CRM that exports one clean record helps with portability, access requests and audits.

Where a rule is still unclear, take the careful reading and confirm with your lawyer. For the system side, ZenWeb’s web development team can help you build it.


9. Frequently Asked Questions

1. Is data portability in force in Malaysia?

Yes. Section 43A of the PDPA came into force on 1 June 2025. As at October 2026, the regulations that set the deadline, fees and covered data have not yet been issued.

2. How long do I have to answer a data portability request?

The law says “within the period as may be prescribed”, and no period has been prescribed yet. The Commissioner’s consultation paper proposed 21 days, plus 14 more days if needed, so that is a sensible target.

3. Do I have to send the data to the customer?

No. Section 43A is about transmitting the data directly to another data controller chosen by the customer. If the customer wants a copy for themselves, that is a data access request under section 30.

4. Can I refuse a data portability request?

The right is subject to technical feasibility and compatibility of the data format, so a transfer that cannot work technically is limited by law. Explain the reason in writing and confirm the position with your lawyer.

5. Can ZenWeb make my CRM portability-ready?

We can build websites and CRM integrations with per-record export, privacy-request forms and role-based access. We handle the system side; please confirm legal obligations with a licensed lawyer.

Cite this page: ZenWeb (2026). Data Portability Under PDPA: What It Means for Your CRM. https://zenweb.my/blog/data-portability-pdpa/

You may quote our data with this credit and a link. See our Terms of Use.

Get a website and CRM that can answer data requests

Talk to ZenWeb about joining your forms, orders and chats into one exportable customer record with secure access. We build the system; your lawyer confirms the legal side.

Book a free consultation →

Table of Contents
Table of Contents

Get A Free Proposal

Complete the form and our team will contact you to discuss your goals. Let’s grow your business.