Case study · 2014 – 2020 (multi-phase)
Pink Group: Salesforce ↔ NetSuite integration for media & ecommerce.
Building a bidirectional Salesforce ↔ NetSuite integration that ended the constant "which system is right?" argument between Sales and Finance — and a foundational pillar of a wider ERP consolidation that took month-end close from 12 days to 2.5.
1The challenge
Pink Group Holdings is a media and ecommerce business with a sophisticated Salesforce CRM driving the sales motion — but historically, a complete disconnect between Salesforce and the NetSuite back office. The symptoms were textbook:
- Customers existed in two systems with different IDs. Sales talked about Customer A by their CRM identifier; Finance talked about the same customer by their NetSuite internal ID. Reports never quite reconciled.
- Opportunities had to be re-keyed as sales orders. The Sales team closed a deal in Salesforce; someone in Finance re-typed it into NetSuite. Typos and transposed line items were inevitable.
- Product catalogue, pricing and master data drifted constantly. Salesforce had its catalogue; NetSuite had a different one. Discounts agreed in CRM didn't always make it onto the invoice.
- Sales and Finance argued. About who the customer was, what they ordered and what they should pay — and which system was right.
2The approach
Salesforce as the CRM front-end of record. NetSuite as the financial and operational system of record. A clean, bidirectional contract between the two — with customer-ID mapping as the foundational piece of plumbing that the rest depends on.
Each system masters the data it's best at. Salesforce masters the relationship and the pipeline; NetSuite masters credit terms, billing addresses, items and pricing. A custom reconciliation flow stamps the matching ID on both sides at the moment of customer creation, so reports never drift apart again.
3What was built
Five bidirectional entity flows, plus the wider ERP consolidation that the integration was foundational to.
Bidirectional entity sync
Capabilities delivered
- Customer-ID mapping — the foundational piece. When a customer is created in either system, the other receives it within seconds with a stable ID mapping stored on both sides. No more reports that don't add up because Sales and Finance are counting different customer entities.
- Opportunity-to-Sales-Order automation — closed-won opportunities in Salesforce trigger a NetSuite Sales Order with the right items, pricing tiers and customer terms, with the Salesforce Opportunity ID stamped onto the order for traceability. No re-keying, no transposed line items.
- Item, product and price-book synchronisation — bidirectional sync of the product master and price-book so Sales is always quoting from the same catalogue Finance invoices from. Discount terms agreed in CRM make it onto the invoice automatically.
- CRM-side relationship history surfaced in NetSuite — Finance can see CRM interaction history, support cases and opportunity pipeline from within NetSuite. Sales can see invoices, payment status and open AR from within Salesforce. One customer conversation, with the right context regardless of who's holding it.
- Wider ERP consolidation — the Salesforce ↔ NetSuite integration was the most visible piece of work, but it was part of a broader programme migrating Sage X3, SAP, Xero, Workday and Concur into a single NetSuite OneWorld estate. I led the technical aspects of the implementation — requirements, solution design, data migration strategy, integration strategy and environment management — and the testing and training across the business.
- Process redesign — alongside the system work, redesigned the O2C, P2P and R2R processes, automated customer and vendor payments, implemented bank payment matching rules, credit assurance and user role audits.
4The outcome
Month-end close: 12 → 2.5 days
The headline result of the wider programme. Finance got their evenings and weekends back. Operations got numbers they could trust the same day Sales reported them.
Single customer record of truth
One customer, one ID mapping, two systems agreeing on every detail. Reports reconcile by design rather than by reconciliation effort.
End of the Sales vs Finance argument
Both teams looking at the same numbers, with role-appropriate views of the same customer record. Disagreements moved from system mechanics to business judgement.
Invoices match what was agreed
Pricing and discount terms set in Salesforce flow through to NetSuite invoices automatically — customer experience improves, queries drop.
Five legacy systems retired
Sage X3, SAP, Xero, Workday and Concur all consolidated into a single NetSuite OneWorld estate — fewer licences, fewer integration points, fewer places for data to drift.
Foundation for growth
The clean integration architecture is what made later phases of the programme possible — including the data migration of Salesforce into NetSuite that followed in the 2020 phase.
5Technologies used
"When Sales and Finance disagree about who the customer is, what they ordered and what they should pay, the business breaks — not catastrophically, just slowly, in ways that are hard to attribute. A properly designed Salesforce ↔ NetSuite integration ends that whole class of problem."