As its contract approached renewal, a software house serving banks and financial institutions opened a market scouting exercise. Its CRM had been running for six years, on premises, across roughly forty seats. The head of procurement describes the practice without drama: whenever a contract nears expiry, they scout for other partners and collect fresh quotations. At that moment changing CRM partner is one option on the table, alongside confirming the incumbent, and many procurement teams open the exercise out of habit rather than conflict.
What follows rarely concerns price. It concerns what happens to the flows, the customised modules and the data already configured: processes are up and running, so does the company rebuild from scratch or start from what exists? Six years of operation put more configuration hours into those flows than the original installation ever did, and nobody wants to pay for them twice.
Here is the short answer before the detail. Data and customisations stay where they are and simply change custodian; flows stay but need rereading; billing of the licence is the only item tied to a date. Rebuilding applies solely to whatever is undocumented or no longer describes how the company works.
Changing CRM partner: licence and support run on different calendars
One clarification comes first, because clients experience two contracts as one. Commercial ownership of the licence moves to a new partner at the end of the current contract cycle. That is the party issuing the invoice for the software subscription. Support, services and consultancy follow a different rule: nothing binds them to that date, and they move whenever the client decides.
Confusion surfaces in almost every call, phrased precisely: if I want to leave a contract, surely I am not tied to the licence expiry. The distinction matters because it sets the calendar for changing CRM partner. A company that wants a new technical counterpart can act immediately; a company that also wants to move licence billing waits for expiry, and renegotiates terms at that point.
Relationships deserve the same care. Before putting a proposal together, the new partner checks the client’s position with the software vendor, then informs the outgoing partner as a courtesy. Certified partners on an enterprise platform form a small market, and working relationships between suppliers outlast any single account. No serious client wants a diplomatic incident between partners, clients and suppliers.
What does a new partner need in order to take over a live CRM?
Three pieces of information: the software version in use, the deployment type together with where the servers physically sit, and the number of active seats.
Cloud versus on premises is no administrative footnote. It determines who reaches the environment and how sandboxes are opened. It also determines which interventions need internal IT and where the data sits for the purposes of the General Data Protection Regulation. The platforms we propose process data in EU datacentres, with certifications in the ISO/IEC 27001 family and requirements aligned to NIS2: the same standards we apply to our own infrastructure, where Aesir Srl operates Tier IV datacentres with replication.
Seat count sizes the training and handover effort, the heaviest line item in any project where a company is changing CRM partner. Forty users spread across sales, marketing and service need a different plan from six users in a single commercial office.
The module that never spoke to the rest of the CRM platform
Long before anyone considered changing CRM partner, marketing at the same company had already been through one migration, from a general-purpose email platform to the marketing automation module of the CRM vendor. Expectations were the obvious ones: staying inside the same suite, lead synchronisation would follow by itself.
It did not. Contacts duplicated, and leads arriving from external portals, loaded at intervals by an ETL process, never reached the commercial platform, so nobody worked them. For a business selling to financial institutions, where a qualified contact opens a long sales cycle, that loss does not come back the following quarter.
Her own reading deserves attention, because it does not blame the supplier: somewhere along the line there was a gap, either in upgrades or in training. That is the point where scouting at renewal stops being a price lever and becomes a technical question. Has the platform been kept current, and have the people been trained on what changed?
Changing CRM partner does not mean rebuilding the flows
Everything starts from what already exists. The incoming partner takes over the current configuration and reads whatever documentation the previous partner or internal staff produced. Next comes the check on whether processes implemented years earlier are still valid or need updating. Only then does anyone build what is missing.
Sometimes a full rebuild is the better call: a sales process designed seven years ago may describe an organisation that no longer exists. That decision belongs to the client, after the review, and no incoming supplier should present it as a precondition.
Changing CRM partner without documentation
Missing documentation is the real risk at this stage. When nobody has documented the configuration, the new partner reconstructs it by examining the environment element by element. Custom modules are opened one at a time, active automations are read, every integration is tested in a sandbox. Those are days of analysis spent before touching anything, and they stretch the period in which two suppliers work on the same system. Ask the incumbent for documentation while the relationship is live, not once it has closed.
Anyone weighing a move also wants proof of capacity: how many certified consultants are assigned, whether the supplier covers strategy as well as delivery, which recent references exist in the same sector. Fair questions, and they belong in the written request for proposal, with names and certifications attached. A written answer can be verified; an answer given in a meeting cannot.
| Element | What happens at partner change | Condition |
|---|---|---|
| Data, history, attachments | Stay inside the company instance | None, the instance belongs to the client |
| Customised modules and fields | The new partner keeps and adopts them | Readable documentation exists |
| Flows and automations | Reviewed before reuse, rebuilt if they no longer fit | They still describe current processes |
| Licence billing | Moves to the new partner | At the end of the contract cycle |
| Support and consultancy | Move when the client decides | No expiry constraint |
Renewals: what stays locked when a company changes CRM partner
Renewal is when a decision about partners becomes operational, so the mechanism deserves attention before scouting opens.
Companies changing CRM partner meet the same subscription structure everywhere. Subscriptions run annually and invoice in advance. They cover version upgrades, bug fixing, cloud platform space and three instances: production plus two separate environments for development and testing. Those two sandboxes explain why a configuration change should never be tested in production. They also explain why a new release takes time to reach users during rollout.
A multi-year commitment locks the discount agreed at signature for the whole term, along with the price. That lock covers list price increases as well, from both the vendor and the reseller. At the following renewal the discount percentage does not reset: negotiation restarts from the previous terms with a contained adjustment. It answers an objection clients raise about the wider market, that heavy discounting to win an account is followed by list pricing at renewal.
Seats and modules: the items to verify upfront
Seat handling rarely changes when a company is changing CRM partner. Additional seats work simply: they join on the terms of the original contract and pay pro rata for the remaining term. A seat can be reassigned to a new person without losing the previous user’s history, and the system audit records every change.
Most modules fall inside the subscription. Included are the connector to mail and calendar clients, APIs without consumption tiers, a mobile application that works offline, and advanced reporting out of the box. Charged separately are the data enrichment plugin and the social selling connector, which also requires the top-tier subscription on the social network itself. Those two lines belong in any offer comparison from the outset.
Checklist before changing CRM partner at contract expiry
- Establish the actual end date of the licence cycle, distinct from the service contract.
- Request configuration documentation from the incumbent: custom modules, automations, live integrations.
- Map integrations towards the ERP platform, portals and ETL processes, naming who maintains each one.
- List implemented processes and mark which ones still describe how the company operates.
- Ask each candidate how many certified consultants they assign and which recent references they hold in your sector.
- Define who delivers training after each version upgrade, and how often.
That last point separates a platform producing reliable data from one accumulating duplicates. A national distributor with three internal staff and three field agents summed up the opposite outcome in five words: no support of any kind. Their enterprise CRM had become a quotation tool, nobody had delivered training, and the review under way was about returning to spreadsheets. A year after signing, the question was no longer which partner to choose but whether to have one at all.
Questions from procurement
Does changing CRM partner interrupt daily operations?
No. The instance stays the same and keeps running through the transition. What changes is the technical contact and, at expiry, the name on the invoice. Handover activities run alongside normal use, without pausing sales.
Can support move while the licence stays where it is?
Yes, and that is the most common scenario when contract expiry is still distant. Support, consultancy and development projects go to a partner other than the one invoicing the subscription, with no particular constraints.
What happens to customisations built by the previous partner?
Customisations stay in the instance and are adopted by the incoming team. Documentation remains the condition: without it, understanding them takes longer, and in some cases redesigning the function beats inheriting it.
Let’s talk
Scouting at renewal creates value even when it ends by confirming the incumbent. It forces a company to reread what the platform is actually doing, which automations have been dormant for years, and which contacts never reach anyone. On the inherited environments we work with at Aesir, our first activity is not technical: we compare what the company believed was configured with what is configured. That comparison almost always produces a list of three or four automations nobody knew were switched off, and fixing them is worth doing regardless of who signs the next contract.
If you would like to explore the subject or assess the situation in your own company, you can fill in the form at the bottom of this page or write to support@aesir-tech.it: we will arrange a free consultation and start from your numbers.