Master data management

Enterprise MDM Implementation: Informatica, Reltio and Veeva Network

Informatica MDM consulting and Reltio MDM implementation: data model, match and survivorship rules, stewardship workflows and feeds to CRM and the warehouse.

Get a free proposal

Tell us what you need. A consultant replies within one working day.

We reply from [email protected], usually within one working day. We do not add you to a mailing list.

01

MDM implementation services for when the platform is the easy part

Buying an MDM platform takes a quarter. Getting a golden record people trust takes longer, and it depends far less on the software than on the decisions behind it: which sources count, how records match, which value wins when sources disagree, and who resolves the cases the rules cannot. Platforms implemented without those decisions end up as an expensive copy of the duplicates they were bought to remove.

Greenwolf designs and builds that layer. We work on Informatica, Reltio and Veeva Network, and on lighter warehouse-based masters when a platform is not yet justified. We design the model, write and tune the match and survivorship rules, integrate the sources, set up stewardship, and build the feeds that carry mastered data to CRM and the warehouse. For the broader service, see master data management services.

02

Do you need an enterprise MDM platform?

Not always. A platform earns its cost when several of these are true:

  • Many source systems create or change the same customer, product or supplier records.
  • Records must be mastered in near real time, not overnight.
  • Several downstream systems, such as CRM, ERP and the warehouse, need the same golden record.
  • You need a stewardship interface, audit trail and change history for compliance.
  • Hierarchies and relationships (accounts, affiliations, households) matter as much as the records themselves.

If you have three or four sources, a batch cadence and one main consumer, a well-built master in your warehouse, with documented match rules and a simple review queue, is often the better first step. It can be moved to a platform later because the rules travel with it. We will tell you which side of that line you are on. For the difference between within-source and across-source mastering, see types of MDM.

03

The platforms we work on

  • Informatica MDM

    Informatica's cloud MDM runs as MDM SaaS inside its Intelligent Data Management Cloud (IDMC), alongside its data integration and data quality services, with Customer 360 as its customer domain. Salesforce completed its acquisition of Informatica in November 2025.

    • Customer 360 and multidomain models
    • Match and merge configuration
    • Integration and data quality on IDMC
  • Reltio

    Reltio is a cloud-native MDM platform, sold as Reltio Data Cloud, with multidomain mastering, a graph model for relationships, industry data models including life sciences, and AgentFlow for AI agents.

    • Entity and relationship modelling
    • Match rules and ML matching
    • Real-time APIs to consumers
  • Veeva Network and OpenData

    Veeva Network is Veeva's multi-domain MDM for life sciences, natively integrated with Vault CRM, and Veeva OpenData supplies HCP and HCO reference data to validate against.

    • HCP and HCO masters
    • Affiliations and hierarchies
    • OpenData change requests
  • Warehouse-based masters

    Masters built in Snowflake, Databricks or Microsoft Fabric with documented rules and review queues, for teams not yet ready for a platform.

    • SQL and Python match logic
    • Steward review queues
    • A path to a platform later

04

Pharma: HCP, HCO and patient masters

Pharma has its own MDM shape. HCP and HCO records arrive from CRM, syndicated data, specialty pharmacies, hubs and claims, each with its own identifiers. Many companies use Veeva Network as the customer master, validated against OpenData or another reference source, and then still need to link that master to the patient-level and specialty pharmacy data that sits outside it. We build those links, and the patient master that has to stay de-identified where the work allows. See customer master data management, patient master data management and Veeva CRM data integration.

05

Matching, survivorship and stewardship

Deciding which records are the same entity

We combine deterministic rules on trusted identifiers (NPI, DEA, tax ID, an internal key) with fuzzy rules on names and addresses and, where the platform supports it, machine learning suggestions. Every rule is tested on a labelled sample so you know its false match and missed match rates before it goes live.

  • Deterministic and fuzzy rules
  • Tested on labelled samples
  • Thresholds agreed with the business

06

Further reading on matching and survivorship

We have written about each of these in more depth: types of matching in MDM, survivorship in MDM and the golden record, and our data stewardship service.

07

What an MDM implementation covers

Source and data profiling

We profile each source for completeness, identifier quality and duplicate rates.

Model design

Entities, attributes, relationships and hierarchies designed for the questions the business needs answered, mapped to the platform's model.

Match and merge rules

Rules written, tested on labelled samples and tuned until false and missed matches sit within agreed thresholds.

Source integration

Batch and real-time integrations from each source.

Stewardship workflows

Review queues, approval steps and audit trails configured.

Downstream feeds

Golden records and cross-references delivered to CRM, ERP and the warehouse.

08

Case snapshot: patient access reporting

A specialty therapy provider rebuilt its patient access reporting by hand each cycle because identifiers did not match between sources. We built clean identifiers and an MDM structure, automated case pipelines, standardised reporting and dashboards, cutting manual work by 60 to 80 percent. For the issues we see most in pharma, read common data quality challenges in pharma MDM.

09

How we work

NDA signed before any data is shared
Built in your platform tenant and cloud, not copied to ours
De-identified data wherever the work allows; PHI only under your Business Associate Agreement
We work with your software vendor or licensing partner; we do not resell licences
Senior-led team in New Delhi, India, with US East Coast and Europe hour overlap; 1,000+ projects for 200+ clients over 8+ years

10

Enterprise MDM questions

What do MDM implementation services include?
Source profiling, data model design, match and survivorship rules, source integration, stewardship workflows and feeds to downstream systems. The platform configuration is one part; the rules and the stewardship process decide whether the golden record is trusted.
Informatica or Reltio: which is better?
Both are established enterprise MDM platforms. The choice usually turns on your existing stack, how much real-time and relationship data you need, and your industry models. Informatica now sits within Salesforce, which matters if Salesforce is central to your estate. We help you test both against your own data before you decide.
What is a customer master data management platform?
It is software that brings customer records from many systems together, matches duplicates, picks the best value for each attribute, and publishes one trusted record to the systems that need it, with a stewardship interface and audit trail.
Do pharma companies need Informatica or Reltio if they have Veeva Network?
Often not for HCP and HCO data, since Network is built for that. Some companies still use an enterprise platform for other domains, such as products, suppliers or patients, or to master data across business units.
Are you an Informatica or Reltio partner?
We do not claim any vendor partnership. We work in the platform you license, alongside your vendor or reseller, on the design, rules, integration and stewardship.

Tell us which records will not match

Describe your sources, the domain you need mastered and where the platform decision stands. We will come back with how we would approach the model, rules and stewardship.

A reply from a consultant, usually within one working day.

Part of our Master Data Management hub. Start with our master data management services.

Master Data Management

More on master data management services

See all of Master Data Management

Get started

Tell us where the week goes

Two weeks, fixed scope, a costed plan at the end. No obligation after it.

  • We map your workflows and where the time actually goes
  • You get the three that cost the most, with what automating them takes
  • Delivered as a document, in 5 to 7 working days

We reply from [email protected], usually within one working day. We do not add you to a mailing list.

Tell us where the week goes

A senior consultant will map where the time goes, name what is worth automating and what it takes. No obligation after it.