
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.
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.
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:
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.
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.
| Date | Milestone | Status |
|---|---|---|
| 2024 | Consultation Paper 03/2024 proposes regulations and a guideline | Proposal only |
| 17 Oct 2024 | Act A1727 published, inserting s.43A | Law passed, not yet in force |
| 1 Jun 2025 | s.43A comes into force with DPO and breach notification rules | In force |
| Oct 2026 | Deadline, fee cap, data whitelist and technical standards | Not 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.
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.
| CRM field | Data type | Likely status |
|---|---|---|
| Name, email, phone from your enquiry form | Provided directly | Likely covered |
| Delivery address and order details | Provided under a contract | Likely covered |
| Member profile and marketing preferences | Provided directly | Likely covered |
| Pages viewed and session recordings | Observed | Open question |
| Lead score and sales stage | Derived | Likely excluded |
| Ad-interest segment or audience tag | Inferred | Likely excluded |
| Paper forms never keyed into a system | Manual records | Likely 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:
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.
| Request | PDPA section | Data goes to | Time limit |
|---|---|---|---|
| Access | s.30–31 | The customer | 21 days, plus 14 if you notify a delay |
| Correction | s.34–35 | The customer (corrected copy) | 21 days |
| Withdraw consent | s.38 | Nobody; you stop processing | On receiving the notice |
| Portability | s.43A | Another data controller | To 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.
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.
| Setup | Readiness score | Main gap |
|---|---|---|
| WhatsApp chats and email only | 2 | No single record; manual copying |
| Shared spreadsheets | 4 | Duplicates across tabs; weak access control |
| Website form plugin storing entries | 5 | Entries not linked to orders or chats |
| Off-the-shelf CRM with contact export | 7 | Export may mix provided and derived fields |
| Integrated CRM with API and field tags | 9 | 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.
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 →
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:
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.
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:
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.
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:
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.
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.
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.
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.
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.
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.
Get A Free Proposal
Complete the form and our team will contact you to discuss your goals. Let’s grow your business.
Chat with us on WhatsApp
Tell us a little about what you need. We'll open WhatsApp with your message ready to send.