What Data Should a Hong Kong NGO CRM Store? A Practical, PDPO-Ready Field Guide

A useful NGO CRM does not try to store everything. It keeps the information the organisation needs to manage relationships, deliver services, raise funds and communicate responsibly—while making the source, permitted use and ownership of that data clear.

For an NGO preparing a database cleanup or CRM migration, the practical question is not “How many fields can we create?” It is “Which information supports a real process, and who is responsible for keeping it accurate?”

Why spreadsheets fail Hong Kong NGOs

Spreadsheets are useful for temporary analysis, but they become risky when several teams use copied files as the organisation’s unofficial database. Donor history, event attendance, volunteer activity and marketing preferences quickly fall out of sync. Staff then spend time checking which file is current—and an opt-out or data correction may not reach every copy.

What should a proper NGO CRM do that Excel cannot?

Excel stores rows. A CRM should manage relationships and the processes around them.

Maintain one person record across donor, volunteer, member and event roles
Show a shared history of interactions, donations and activities
Control ownership, permissions and approved values
Apply communication preferences and opt-outs consistently
Trigger follow-up tasks and produce current operational reports

What does a practical NGO CRM usually look like?

Most NGOs work with the same person in more than one capacity. Someone may be a donor, volunteer, event attendee and newsletter subscriber. A well-designed CRM keeps one contact record and connects it to the person’s different relationships and activities.

Contacts: donors, volunteers, members, participants and supporters
Organisations: companies, foundations, schools, government bodies and partners
Transactions: donations, pledges, memberships and grants
Activities: events, campaigns, volunteer assignments and programme interactions
Communication preferences: subscriptions, permitted channels and opt-out status
Governance information: collection source, record owner, review date and access level

Illustration_1_NGO_CRM_Data_Model

The exact structure should follow the NGO’s services and operating model. A fundraising charity and a social-service organisation will not need identical databases.

Which fields should an NGO CRM contain?

Start with a small core set. Add a field only when it supports a defined workflow, report, decision or legal requirement.

1. Identity and contact

Full name and preferred name
Email address and telephone number
Preferred language and communication channel
Organisation and role, when relevant

2. Relationship and fundraising

Stakeholder type, such as donor, volunteer or member
Relationship status and assigned staff owner
Donation, membership, event or volunteer history
Campaign, appeal or programme association

3. Communication and marketing

Subscription or marketing status
Permitted communication channels
Consent or indication-of-no-objection record, where applicable
Opt-out date, source and scope

4. Data governance and migration

Original collection source and collection date
Collection purpose or permitted use
Legacy system ID and migration batch
Data owner, access level and next review date
Duplicate, incomplete or cleanup status

VM BLOG BANNER (11)-1

What should stay outside the general CRM?

Centralisation does not mean putting every document and sensitive detail into one database. Information should be excluded or stored in a more restricted system when the general CRM does not need it.

Detailed beneficiary or case notes
Medical, counselling or safeguarding information
Copies of identity documents unless clearly required
Banking details and full payment-card information
Unstructured staff comments with no defined operational purpose

The CRM can often store a relationship status, case reference or next action without holding the underlying sensitive file.

What should you clean before migration?

Do not migrate every spreadsheet unchanged. Before importing data, work through these decisions:

Identify the authoritative source for each type of information.
Merge duplicate people without losing their donation or activity history.
Standardise field names, formats and dropdown values.
Separate confirmed marketing status from unknown or unreliable values.
Remove obsolete fields and records that no longer serve a defined purpose.
Assign an owner and review rule to every field that remains.

How does PDPO affect CRM design?

Hong Kong’s Data Protection Principles cover matters including collection, accuracy, retention, use, security, transparency, access and correction. In practical CRM terms, an NGO should be able to explain why a field exists, where its value came from, who may use it, how it is kept accurate and when it should be reviewed or removed.

Fundraising messages may also fall within the direct-marketing regime. The CRM therefore needs a reliable way to record the relevant notification, response, permitted use and opt-out—not merely a single unchecked “consent” box.

See the PCPD’s overview of the Personal Data (Privacy) Ordinance and Guidance on Direct Marketing for the formal requirements.

Illustration_3_Permission_Workflow

How should Hong Kong NGOs think about AI and PDPO?

For Hong Kong NGOs, the issue is not whether AI should be used at all, but whether it is used inside a governed environment with clear controls over data access, model training and sensitive information. Staff should not paste donor or beneficiary information into uncontrolled public AI tools simply because the tool is convenient.

HubSpot’s AI settings allow Super Admins to manage whether AI can access CRM data, customer conversation data and files data. They can also turn off AI model training at account level while continuing to use AI features. Accounts with HubSpot Sensitive Data enabled are opted out of AI model training by default and cannot opt in while that setting is enabled.

HubSpot also states that third-party AI service providers engaged to deliver its subscription services are not permitted to use customer data for model training, with data retention minimized and zero retention used where possible. These controls create a more governable foundation than ad hoc use of consumer AI tools, but they do not make an NGO automatically PDPO-compliant.

Compliance still depends on what data the NGO collects, what users and AI features can access, what is shared with service providers, and how permissions, retention and internal policies are managed. The safer approach is to begin with approved use cases, minimum necessary data and documented human oversight.

VM BLOG BANNER (10)-1

Use a lightweight data dictionary

Before configuring or migrating the CRM, create one row for every proposed field and record:

Field name and business definition
Example value and accepted format
Required, optional or restricted status
Source system and business owner
Who can view or edit it
Migration, review and retention rule

If nobody can explain how a property will be used or maintained, it probably should not be migrated yet.

Where does HubSpot fit for Hong Kong NGOs?

HubSpot can be configured as the central relationship database for donors, volunteers, members, corporate partners and event participants. Custom properties can reflect the NGO’s field definitions, while connected records and workflows can support follow-up, segmentation and reporting.

The important step is to design the data model and operating rules before configuration. HubSpot does not decide what an NGO should collect, who should access it or how long it should be retained. Explore HubSpot for NGOs in Hong Kong for a practical implementation framework.

Frequently Asked Questions

Should donors, volunteers and members be stored in separate databases?

Usually not. One person record with multiple relationship types gives the NGO a clearer history and reduces duplicates. Access to sensitive programme information can still be restricted.

What are the minimum fields for a new NGO CRM?

Start with identity, contact details, stakeholder type, relationship status, record owner, collection source, communication status and a review date. Add programme-specific fields only when a defined process needs them.

Should every old record be migrated?

No. Records with no clear source, purpose, owner or continuing operational value should be reviewed before migration. Moving poor-quality data into a new CRM only makes the problem harder to see.

Why do Hong Kong NGOs need a CRM instead of Excel?

A CRM gives the team one controlled relationship history, clear ownership and repeatable workflows. Excel remains useful for analysis, but it is difficult to use as a shared operational system across fundraising, marketing, events and volunteer management.

What is the best CRM for a Hong Kong NGO?

The best CRM is the one that fits the NGO’s processes, budget, reporting needs, integrations and staff capacity. Compare platforms only after defining the required data model, permissions, workflows and migration scope.

Can HubSpot manage donors, volunteers and events in one database?

Yes, when the data model is designed correctly. One contact can hold several relationship types, while properties, activities and connected records track donations, volunteer work, event participation and communication preferences.

How do Hong Kong NGOs move from Excel to a CRM without losing data?

Start by keeping an untouched backup, identifying the authoritative spreadsheet for each data category and mapping every source column to a defined CRM field. Clean duplicates, test a small migration batch and reconcile record counts, donation totals and sample histories before moving the remaining data.

What is the best CRM structure for a Hong Kong nonprofit?

Use one contact record for each person, with multiple relationship types when someone is both a donor, volunteer, member or event participant. Connect contacts to organisations, donations, activities, communication preferences and governance information instead of creating separate copies in different databases.

What donor and volunteer data should not be stored in a general CRM?

Avoid storing identity-document copies, full payment details, sensitive case or health information, safeguarding records and informal staff comments by default. When such information is genuinely required, use a suitably restricted system or store only a controlled reference or status in the general CRM.

How should a Hong Kong NGO track PDPO-related communication permissions?

Record the communication purpose, channel, current status, source, date, notice or form version and supporting response. Also record the date and scope of any opt-out, then use suppression workflows so the preference is applied consistently across connected marketing and fundraising tools. The exact process should be reviewed against the NGO’s notices and activities.