Moving your processing register out of Excel: what to clean first

Before moving a processing register out of Excel, keep one row per processing activity, one column per Article 30 field (purpose, people, data, recipients, transfers, retention, security), clear column headers, no merged cells and no notes inside the data. Save an archived copy of the old file with its date, then import and review each activity rather than copying blindly.
Many companies start their GDPR record of processing activities in a spreadsheet. That is allowed: Article 30(3) only asks for the record to be "in writing, including in electronic form". The trouble starts later, when the file has grown, several people have edited it and nobody is sure which version is current.
Moving to a register tool fixes that, but only if the data you bring is clean. This guide covers what a register must contain, how to shape your spreadsheet before importing it, and what to check afterwards. It is general guidance, not legal advice.
#What must a processing register contain?
Article 30(1) of the GDPR lists what a controller records for each processing activity. The CNIL describes the same list as one "fiche" per activity. Your spreadsheet should have one column for each of these points:
| Article 30(1) point | What to put in the column | Example |
|---|---|---|
| (a) Controller and contacts | Your company, joint controller, representative, DPO | Acme SAS, DPO: dpo@acme.com |
| (b) Purposes | Why you process the data | Pay employees |
| (c) People and data | Categories of data subjects, categories of personal data | Employees; identity, salary, bank details |
| (d) Recipients | Who receives the data, including processors | Payroll provider, accountant |
| (e) Transfers | Countries outside the EEA and the safeguard used | United States, standard contractual clauses |
| (f) Retention | How long each category is kept, or the criteria | 5 years after the end of employment |
| (g) Security | A general description of the measures | Access limited to HR, two-step sign-in |
Point (a) is usually the same for every row, so it can live once at the top of the register rather than in every line. A legal basis column is not listed in Article 30, but most registers keep one because the privacy policy needs it anyway.
#Do small companies need a register at all?
Often, yes. Article 30(5) exempts organisations with fewer than 250 people only when the processing is occasional, unlikely to create a risk for people, and does not include special categories of data or criminal records. Payroll, customer accounts or a newsletter are not occasional. The CNIL recommends recording any processing you are unsure about. Our guide to Article 30 for small businesses goes through the test.
#How should the spreadsheet look before you import it?
Import tools read tables, so the closer your file is to a plain table, the less you fix by hand afterwards.
- One row per processing activity. Not one row per tool, per department or per data category. "Payroll" is one row, even if three tools are involved.
- One header row, in plain words. "Purpose", "People concerned", "Retention period". A title above the table is fine; a second header row or a header split over two lines is not.
- No merged cells. Merged cells read as empty in every row but the first.
- One value type per column. Retention goes in the retention column, not in a comment on the purpose.
- Recipients named the same way everywhere. "Google Workspace" in one row and "GSuite" in another become two different recipients.
- Notes kept apart. Put your working notes in a separate sheet or column you leave out of the import.
No register yet? Our free record of processing activities template already has these columns, with three filled examples.
If your register follows the CNIL model, with one sheet per activity and labels on the left, that layout can also be read: each sheet becomes one activity. The CNIL's simplified template is published as an ODS file, so save it as .xlsx or .csv first if your tool only reads Excel files.
#What should you clean first?
Most registers kept in a spreadsheet drift in the same ways. Fix these before the import, while you can still sort and filter the whole file:
- Duplicates. Sort by activity name and merge rows that describe the same processing.
- Vague purposes. "Marketing" or "Administration" is too broad. Split it into what you actually do: newsletter, events, invoicing.
- Missing retention. Article 30 asks for it "where possible". An empty cell is the most common gap in audits; write at least the rule you follow.
- Old tools. Remove recipients you no longer use, and add the ones you do.
- Transfers. For each recipient outside the EEA, note the country and the safeguard, such as an adequacy decision, the EU-US Data Privacy Framework or standard contractual clauses.
- Sensitive data. Mark rows that involve health, biometric or other special categories: they often need an impact assessment.
#What should you keep from the old file?
Do not delete the spreadsheet once the import is done. Save a copy with its date, read-only, as the history of your register before the move. If an authority or a customer asks how your records looked at a given date, that copy answers. From then on, keep the register in one place only, so there is never again a "latest version" question.
#Where does Privacyboard fit?
Privacyboard can import a register from an Excel or CSV file. It recognises column headers in English and French, shows which column it matched to each field so you can correct it, and leaves activities already in your register unticked. Tools named in a recipients column are linked to the vendors you already listed. See Import an existing register.
#Checklist before and after the import
- One row per activity, one header row, no merged cells.
- Columns for purpose, people, data, recipients, transfers, retention and security.
- Duplicates merged and vague purposes split.
- Retention filled for every activity, at least as a rule.
- Recipients named consistently, old tools removed.
- Transfers outside the EEA noted with their safeguard.
- A dated, read-only copy of the old file kept.
- After the import: each activity opened and checked, empty fields completed.
- Rows with sensitive data screened for an impact assessment.
#FAQ
#Is a spreadsheet a valid GDPR register?
Yes. Article 30(3) accepts a written record "including in electronic form". What matters is that it is complete, current and available to the authority on request.
#Can I import the CNIL template directly?
The CNIL publishes its simplified register model as an ODS file. Save it as .xlsx or .csv first if your tool reads only those formats. Its one-sheet-per-activity layout can then be read as one activity per sheet.
#Should the register list tools or activities?
Activities. A tool is a recipient inside an activity. Listing tools instead of activities makes the purposes and retention impossible to state clearly.
#Do I need a legal basis column?
Article 30 does not list it, but most registers include it because the privacy policy has to state the legal basis of each purpose. Keeping it in the register avoids writing it twice.
#What if my spreadsheet has several sheets?
Keep the activities in one table, or use one sheet per activity with the same labels on each. Sheets that mix both are the hardest to import.
#Sources
- Regulation (EU) 2016/679 (GDPR), Article 30, EUR-Lex.
- CNIL, Le registre des activités de traitement, read 13 November 2026.
Privacyboard is a guidance tool, not legal advice. This article explains general rules in plain language and was accurate on the date above; laws and guidance change. For an unusual situation, ask a qualified professional. Spotted a mistake? Write to hello@privacyboard.io.


