Under one roof with Microsoft Dynamics 365
In enterprise accounts Dynamics 365 is already in place. Our question was never how to replace it, but how to make it share one customer profile with the 1page ecosystem.
In most of our enterprise accounts Dynamics 365 has been running for years and the teams know it well. In that situation the right question is not "which one do we pick?" but "are these two talking about the same customer?".
One profile, two pillars
In the architecture we built, sales and service records on the Dynamics side meet behaviour, campaign and loyalty data on the 1page side under a shared customer identity. A sales rep sees the campaign history without leaving their own screen; the marketing team can take an open service ticket into account while building a segment.
Our favourite part of this approach is that nobody has to break a habit. Teams keep working in the screen they know — the only thing that changes is that the screens now tell the same truth.
Where we draw the line
In practice we set a division of labour: enterprise processes such as contracts, quotes, service tickets and the sales pipeline stay on the Dynamics side; behavioural data, campaign design, loyalty mechanics and the customer-facing mobile experience live on the 1page side. Each side does what it is strong at.
When building the bridge, what we watch most closely is that synchronisation is one-way and explicit. Which field is authoritative in which system is written down; in projects with two-way, rule-free sync, the systems overwrite each other endlessly and nobody can say which record is current.
This setup has one more benefit for enterprise buyers: the existing Dynamics investment is not thrown away. Instead of migrating to a new platform, you complete what the current one cannot see.
