CRM — Customer Relationship Management

CRM (Customer Relationship Management) describes software that organises customer-facing data and processes: contact data, sales pipeline, opportunities, quotes, after-sales support, marketing campaigns. Where ERP manages internal operational data, CRM manages external customer interaction. In the mid-market in Germany, Switzerland and Austria, CRM is increasingly delivered as an integrated module of the ERP, though dedicated platforms like Salesforce or HubSpot still dominate larger or sales-driven organisations. The boundary between CRM and ERP has blurred over the past decade: order-management functions historically belonging to ERP are now offered by sales-led CRM platforms, while integrated CRM modules in ERP suites have closed much of the experience gap to dedicated platforms.

Core CRM modules

• Contact and account management: master data for individuals and the companies they represent
• Sales pipeline: opportunities tracked through stages, with forecast roll-up
• Quote and order management: configurable quotes, conversion to orders, integration with ERP for fulfilment
• Marketing automation: email campaigns, lead scoring, landing pages
• Service and support: ticketing, SLAs, knowledge base, customer portal
• Analytics: pipeline reports, sales-rep performance, customer-lifetime-value calculations

Integrated vs standalone CRM

An integrated CRM module inside the ERP shares master data — customer record, address, credit limit, order history — without synchronisation issues. This is the path of least friction for mid-market companies up to roughly 200 employees with a sales team of 5-20 people. Standalone CRM (Salesforce, HubSpot, Pipedrive, Zoho) becomes attractive when sales-team size exceeds the integrated solution's sweet spot, marketing automation needs are heavy, or the company is sales-led rather than operations-led.

Selection criteria

When choosing CRM for an operation in Germany, Switzerland and Austria, evaluate (1) German-language support and localised templates, (2) GDPR-compliant data handling and EU-region hosting, (3) integration with the ERP — bidirectional sync of customer master data, orders, and invoices, (4) email integration with Outlook and Gmail, (5) telephony integration if your sales team uses calls heavily, (6) total cost over three years. Per-user pricing ranges from 20 EUR/month (basic CRM) to 250 EUR/month (Salesforce Enterprise).

CRM-ERP integration patterns

Three architectures cover almost all DACH mid-market deployments. Embedded CRM module in the ERP: Microsoft Dynamics 365 Sales with Business Central, SAP S/4HANA with C/4HANA Sales Cloud, abas CRM, weclapp CRM, Sage X3 CRM. Shared customer master, no synchronisation overhead, the path of least friction. Tightly integrated separate stack: dedicated CRM (Salesforce, HubSpot, Pipedrive) with bidirectional sync to the ERP via prebuilt connectors or an iPaaS layer. Customer master usually lives in the CRM and propagates to the ERP, with invoicing and orders syncing the other way. Typical sync intervals: real-time for orders, near-real-time for opportunities, hourly batch for master-data drift. Loose integration: CRM and ERP exchange minimal data — new customer record, occasional order status — usually via simple REST endpoints. Acceptable for service companies with low transaction-volume per customer; rarely sufficient for B2B distribution or manufacturing. Key trade-off: a deeper integration requires investment but eliminates data discrepancies that drive sales-finance conflicts. Implementation effort for full bidirectional sync between Salesforce and SAP S/4HANA: 200–500 person-days; for HubSpot and Microsoft Dynamics 365 BC via prebuilt connector: 30–80 person-days.

GDPR and data-protection specifics for CRM

CRM systems are a high-risk category under the EU General Data Protection Regulation because they process personal data of prospects, contacts and individual buyers at scale. DACH-relevant compliance dimensions: (1) Lawful basis for processing: legitimate interest for B2B prospecting in Germany is generally accepted under recital 47 GDPR, but only with documented balancing tests and clear opt-out paths. (2) German UWG e-mail rules: B2B cold email is acceptable under section 7 UWG only when there is a substantive business connection; B2C cold email requires prior consent (opt-in). (3) Data residency: EU-region hosting is now a default expectation. Salesforce and HubSpot offer Frankfurt and Dublin instances; Microsoft Dynamics 365 has the Germany and Switzerland sovereign clouds. (4) Right of access and erasure: GDPR Article 15 and 17 obligations require the CRM to produce and delete a person's full record on request — including activity history, emails, call logs, contract documents. Mature CRMs automate this; legacy custom CRMs often do not. (5) Data Processing Agreement (DPA): required with every CRM vendor that processes personal data on the company's behalf. The DPA terms restrict sub-processor use, set incident-notification timelines, and define data-deletion at contract end. Annual GDPR audit attention to CRM is meaningful in DACH operations — especially when sales reps export contact data into local spreadsheets, the most common GDPR shadow-IT issue.

Related Topics

• ERP
• ERP vs CRM
• CRM software overview