Should Your CRM Be the System of Record for Client Data? A Guide for Wealth Firms
CRM, portfolio system or a separate MDM hub: which should own client data? Compare what each costs to build and run, and see where Swiss, EU and DIFC rules decide for you.
The real choice behind a wealth management CRM integration
Every wealth management CRM integration project hits the same question early: when a client's address, tax residency or risk profile changes, which system's version is right? Usually nobody has written down the answer. So the CRM, the portfolio management system, the core banking platform and the onboarding tool each keep their own copy. Relationship managers fix records in one place, operations fixes them in another, and auditors find the mismatches.
Picking a golden source for client data is a governance decision first and a technical one second. Firms tend to land on one of three patterns: the CRM as master, the portfolio or core system as master, or a separate client master data management (MDM) hub. Each moves cost, risk and regulatory exposure to a different place. The right pick depends on how many booking centers you run, how tightly your client data is regulated, and which system operations actually trusts.
When the CRM should own the client record
With CRM as master, client and household data is created and maintained in the CRM, for example Salesforce Financial Services Cloud or Microsoft Dynamics 365. It's then pushed to the portfolio system, custodian feeds and reporting. Onboarding workflows, KYC refresh tasks and relationship hierarchies live where advisors already work.
This fits independent advisors, multi-family offices and smaller wealth managers best. They often book through third-party custodians and run no core banking system, so the CRM is the most complete record of who the client is. Setup is quick because most CRMs ship with household and relationship data models.
The weakness is control. CRMs are built so many users can edit records easily, which is the opposite of what you want for legal entity data, tax identifiers and account ownership. Without field-level permissions, approval workflows and an audit trail, a CRM master slowly becomes a record anyone can overwrite.
When the portfolio or core banking system should be master
Private banks and larger wealth managers usually make the booking system the master: Avaloq, Temenos, SS&C, Objectway or a similar portfolio or core platform. The legal client record, account structure and mandate sit where transactions settle. The CRM gets a read-only or partly editable copy through CRM portfolio system integration.
This matches how regulators and auditors think. The record that drives statements, tax reporting and transaction monitoring is also the master, and most core systems already have the maker-checker controls CRMs lack.
The cost lands on the front office. Core platforms change slowly. Prospect and pre-onboarding data has no natural home, and advisors who can't fix a phone number in the CRM will start keeping spreadsheets. The pattern only works with a clear split: the core owns legal and regulatory attributes, the CRM owns relationship, preference and pipeline data, and changes flow back through a controlled change-request process.
When a separate MDM hub earns its cost
A dedicated client MDM hub, from vendors such as Informatica, Reltio, Semarchy or Profisee, sits between all the systems. It matches duplicates, applies a survivorship rule to each attribute and publishes the golden record to every consumer.
It's justified when you run several booking centers or core systems, often after an acquisition, and no single system holds a complete view of the client. A firm with Swiss, Luxembourg and Singapore entities on different platforms is the classic case.
For a single-entity firm it's usually overkill. You add a platform, a data stewardship team and another integration layer. That pays off only if duplicate and conflicting records already cost you money in operations rework, failed KYC reviews or misdirected client communications.
What each pattern costs to integrate and run
The figures below are indicative 2026 market ranges for a mid-sized wealth firm with roughly 5,000 to 50,000 clients. They vary widely by contract, region, systems integrator and data quality, so confirm them with vendors and partners.
| Pattern | Initial integration (USD) | Annual run cost (USD) | Typical timeline | Main cost driver |
|---|---|---|---|---|
| CRM as master | $80k–$250k | $30k–$100k plus CRM licenses | 3–6 months | Building controls and audit trails into the CRM |
| Portfolio/core as master | $120k–$400k | $50k–$150k | 4–9 months | Core vendor change requests and API fees |
| Separate MDM hub | $400k–$1.5M | $150k–$600k including license and stewards | 9–18 months | Matching rules, data cleansing, stewardship staff |
Say a hypothetical firm has 12,000 clients and a meaningful share of duplicate records across two systems. Cleansing alone could occupy a couple of analysts for several months, whichever pattern it picks. Budget for cleanup separately; integration quotes rarely include it.
Where data-residency rules change the answer
Regulation can rule out a pattern before cost comes up. Rules differ a lot by jurisdiction, so have local counsel review your design. Here's how the main regimes generally play out.
- Switzerland: Banking secrecy under the Banking Act and FINMA's expectations on client identifying data (CID) push banks to keep identifying data in Switzerland or pseudonymize it before it leaves. A global SaaS CRM as master is often hard to defend. Swiss private banks usually keep the core as master and send the CRM masked or tokenized identifiers.
- European Union: GDPR doesn't require data to stay in-country, but transfers outside the EU need a lawful mechanism such as an adequacy decision or standard contractual clauses. DORA adds ICT third-party risk obligations for financial entities and their providers. An MDM hub that copies personal data into every connected system multiplies your processing records and transfer assessments. Some member states, Luxembourg for example, add professional secrecy duties.
- DIFC and wider Gulf: The DIFC Data Protection Law and DFSA outsourcing requirements generally allow cloud hosting, but expect documented transfer safeguards and regulator access. Onshore UAE and Saudi rules can be stricter for some data categories, so a group spanning DIFC and onshore entities may need region-specific instances.
- Elsewhere: Singapore's MAS outsourcing and technology risk guidelines, and India's localization rules for payment data, add constraints that vary by entity type.
In practice, the stricter your strictest jurisdiction, the more likely the master stays on a locally hosted core system or a regional MDM instance, with the CRM consuming a reduced data set.
Red flags in vendor proposals
- A vendor says its product "can be the master" but can't show attribute-level ownership, approval workflows or field-level audit history.
- The quote assumes real-time APIs, but your core vendor offers only nightly batch files or charges per API call.
- There's no survivorship logic. "Last update wins" will overwrite good data with bad.
- Hosting regions are vague, or the vendor can't say where backups, logs and support-staff access sit.
- Data cleansing, stewardship staffing and reconciliation are missing from the total cost.
- The MDM business case counts benefits from systems you haven't connected yet.
A decision rule for choosing your golden source
Start with a one-page attribute ownership matrix. List roughly 40 to 60 client attributes, from legal name and tax residency to communication preferences. Mark which system creates each one, which changes it, and which jurisdictions restrict it. The answer is usually obvious once it's on paper.
The rule: if you book through custodians in one or two jurisdictions with light secrecy rules, make the CRM master and invest in its controls. If you run your own core banking or portfolio platform, or any Swiss or similarly secrecy-bound entity, make the core master and treat the CRM as a governed consumer. Add an MDM hub only when three or more systems hold conflicting legal client records. Before signing, ask every shortlisted vendor to walk through your ownership matrix live, attribute by attribute.
Quick answers
Can we make the CRM master for some attributes and the core system master for others?
Yes, and most mature firms end up there. The core owns legal, tax and account attributes; the CRM owns relationship, preference and pipeline data. It works only if ownership is written down per attribute and enforced in the integration, so neither side can quietly overwrite the other.
How much does a client MDM hub cost for a mid-sized wealth manager?
Typical 2026 market ranges are roughly $400,000 to $1.5 million to implement and $150,000 to $600,000 a year to run, including licenses and stewardship staff. Pricing varies by vendor, record volume and region, so get quotes based on your own data.
Does GDPR require us to host client data inside the EU?
Not as such. GDPR allows transfers outside the EU with a lawful mechanism, such as an adequacy decision or standard contractual clauses plus a transfer assessment. Sector secrecy rules, national laws or your own risk policy may still push you toward EU hosting, so check your setup with qualified counsel.
Can a Swiss private bank use a global SaaS CRM?
Many do. The usual approach is to keep client identifying data in a Swiss-hosted core system and send the CRM only pseudonymized or tokenized data, or to use a Swiss-hosted CRM instance. Whether a given design is acceptable depends on your FINMA obligations and legal advice.
Should integration be real-time or batch?
Use real-time or event-driven integration for attributes that drive client service and compliance, such as address, contact details and KYC status. Positions, performance and less critical attributes can usually move in batch. Check what your core vendor's APIs support, and what they charge, before committing to real-time.
Who should own client master data inside the firm?
Usually a data owner in operations or client lifecycle management, backed by named data stewards, rather than IT or the front office alone. The owner approves changes to ownership rules and survivorship logic. Without that role, every pattern drifts back toward duplicate and conflicting records.
Written by the Smartnode Suite editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.