
Sitefinity
We have run Sitefinity environments integrated with Dynamics 365, and migrated them to HubSpot when a simpler, more connected platform made sense.
What it is good at.
It fits a Microsoft estate
Built on .NET, so it sits inside the same identity, hosting and integration story as the rest of your stack rather than beside it. For an organisation that is Microsoft everywhere, that is worth real money in integration time.
Personalisation without a second platform
Audience segments and personalised content are native rather than an add-on, which keeps the number of systems your marketing team has to learn down.
There is a vendor to call
Commercial support, a published roadmap and a company on the other end of a contract. Some organisations cannot buy software any other way, and that is a legitimate requirement rather than a preference.
Done properly, it buys you this.
- A CMS that lives inside your Microsoft estate rather than next to it
- Dynamics 365 integration without a middleware layer to maintain
- Vendor support and a roadmap, which procurement usually needs to see
- Personalised content without buying a separate platform for it
What KODA does with Sitefinity.
- Sitefinity support
- Sitefinity + Dynamics 365 integrations
- Migrations to HubSpot
25+ years of design and digital work, a HubSpot partner, and one senior team from strategy through to the work that ships. The person who scopes your project is the person accountable for it.
Stay on Sitefinity or move?
It depends how much of it you actually use. We have run Sitefinity integrated with Dynamics 365, and we have moved organisations off it to something simpler and better connected. Both were the right call at the time, and the difference was usually how deep the integrations went.
What a project looks like
A licence and usage audit first: what you are paying for against what is switched on. That answer tends to decide the rest. Then either support and development where you are, or a scoped migration with the integrations mapped before anything moves.
Where it begins
Tell us the version and what it is integrated with. Those two answers usually settle the recommendation in one conversation.
Sitefinity in the wild.
Before you get in touch.
Our licence is up for renewal. Should we renew?
It depends on what you are using. We audit the licence against actual usage before you commit to another term, because that is a decision that is difficult to unwind for a year or more.
Can you support our existing Sitefinity site?
Yes. We have run Sitefinity environments including the Dynamics 365 integration, so this is not a platform we would be learning on your project.
How hard is a move to HubSpot?
The content moves without much drama. The work is in the integrations, particularly anything talking to Dynamics, and in making sure nothing that currently depends on the site quietly stops working. We map that first and quote from it.
