--- title: "Migrating to Ivanti Neurons: 10 Lessons Learned from Cherwell, ServiceNow and Other ITSM Migration Projects" description: Discover 10 lessons learned from successful ITSM migration projects. Practical guidance for organisations migrating from Cherwell, ServiceNow or other platforms to Ivanti Neurons. image: https://pathfinderspecialists.com/hubfs/hs-generated-images/Three%20Consultants%20Planning%20ITSM%20Migration%20at%20Whiteboard.webp --- [Skip to content](https://pathfinderspecialists.com/pathfinder-specialists-blog/migrating-to-ivanti-neurons-10-lessons-learned-from-cherwell-servicenow-and-other-itsm-migration-projects#main-content) [![Pathfinder Specialists Logo - Light](https://pathfinderspecialists.com/hs-fs/hubfs/Copy%20of%20Pathfinder%20Specialists%20Logo%20-%20Dark%20(2).png?width=1295&height=377&name=Copy%20of%20Pathfinder%20Specialists%20Logo%20-%20Dark%20(2).png)Homepage](https://pathfinderspecialists.com/en-gb/home) - [Home](https://pathfinderspecialists.com/en-gb/home) - [Services](https://pathfinderspecialists.com/services) - [Ivanti Neurons](https://pathfinderspecialists.com/ivanti-partner-uk) - [Ivanti Consultancy](https://pathfinderspecialists.com/en/services/ivanti-neurons-consultancy) - [Ivanti Migration Services](https://pathfinderspecialists.com/services/ivanti-migration-services) - [ITSM Consulting](https://pathfinderspecialists.com/services/itsm-consulting) - [MSP Consulting](https://pathfinderspecialists.com/services/msp-consulting) - [Platform Optimisation](https://pathfinderspecialists.com/services/platform-optimisation) - [Resource Augmentation](https://pathfinderspecialists.com/services/resource-augmentation) - [Success Stories](https://pathfinderspecialists.com/success-stories) - [Insights](https://pathfinderspecialists.com/pathfinder-specialists-blog) - Company - [About Pathfinder](https://pathfinderspecialists.com/en-gb/about-us) - [Contact Us](https://pathfinderspecialists.com/en-gb/contact-us) [Contact Us](https://pathfinderspecialists.com/en-gb/contact-us) - [Home](https://pathfinderspecialists.com/en-gb/home) - [Services](https://pathfinderspecialists.com/services) - [Ivanti Neurons](https://pathfinderspecialists.com/ivanti-partner-uk) - [Ivanti Consultancy](https://pathfinderspecialists.com/en/services/ivanti-neurons-consultancy) - [Ivanti Migration Services](https://pathfinderspecialists.com/services/ivanti-migration-services) - [ITSM Consulting](https://pathfinderspecialists.com/services/itsm-consulting) - [MSP Consulting](https://pathfinderspecialists.com/services/msp-consulting) - [Platform Optimisation](https://pathfinderspecialists.com/services/platform-optimisation) - [Resource Augmentation](https://pathfinderspecialists.com/services/resource-augmentation) - [Success Stories](https://pathfinderspecialists.com/success-stories) - [Insights](https://pathfinderspecialists.com/pathfinder-specialists-blog) - Company - [About Pathfinder](https://pathfinderspecialists.com/en-gb/about-us) - [Contact Us](https://pathfinderspecialists.com/en-gb/contact-us) [Contact Us](https://pathfinderspecialists.com/en-gb/contact-us) ![](https://pathfinderspecialists.com/hs-fs/hubfs/hs-generated-images/Three%20Consultants%20Planning%20ITSM%20Migration%20at%20Whiteboard.webp?width=1536&height=1024&name=Three%20Consultants%20Planning%20ITSM%20Migration%20at%20Whiteboard.webp) IT Service Management (ITSM) Ivanti Neurons # Migrating to Ivanti Neurons: 10 Lessons Learned from Cherwell, ServiceNow and Other ITSM Migration Projects ![Sarah Thompson](https://app.hubspot.com/settings/avatar/11ec6208f0bb46e916807b41ad2c1801) Sarah Thompson October 16, 2026 **By Sarah Thompson, Founder & Lead Specialist, Pathfinder Specialists** IT Service Management (ITSM) · Ivanti Neurons · Migration Services Approximate reading time: 11 minutes Successful ITSM migrations depend on people, processes and preparation as much as the technology you choose. A new platform cannot resolve unclear ownership, inconsistent service definitions or unreliable data by itself. Those issues need attention before configuration starts. For organisations migrating from Cherwell, ServiceNow or another platform, the practical questions are similar: what should change, what must be preserved, and how will services continue during transition? This guide sets out 10 lessons to apply when migrating to Ivanti Neurons, with examples illustrating the decisions behind each one. [Pathfinder Specialists](https://pathfinderspecialists.com/) brings service management and platform experience to migration planning, delivery and adoption. The examples below are illustrative scenarios, not claims about named client projects. ## Why Organisations Migrate to Ivanti Neurons An Ivanti Neurons migration can support modernisation, automation and wider service management transformation. Start by identifying which outcomes matter to your organisation, then assess how the proposed platform, operating model and implementation scope will support them. - **Modernisation:** review accumulated customisation and replace outdated ways of working with a maintainable design. - **Automation:** reduce repetitive routing, approval and fulfilment activity where the rules are understood and exceptions are controlled. - **Self-service:** give employees clearer request journeys and accessible answers, supported by useful knowledge. - **AI readiness:** establish trusted knowledge, consistent classifications, appropriate access and human oversight before introducing AI-assisted service delivery. - **Enterprise Service Management:** consider a shared platform for IT, HR, facilities and other teams while preserving appropriate confidentiality and ownership. - **Improved reporting:** agree common service definitions and measures so leaders can compare performance meaningfully. - **Platform consolidation:** reduce fragmented tooling without overlooking customer separation, specialist requirements or ongoing support obligations. Our article on [common ITSM challenges](https://pathfinderspecialists.com/pathfinder-specialists-blog/common-itsm-challenges-and-how-ivanti-neurons-helps-solve-them) explores the operational problems these capabilities can address. Confirm product capabilities, licensing and integration requirements against your intended deployment rather than assuming every feature is included. ## 10 Lessons for Your ITSM Migration Project A controlled ITSM migration project needs evidence at each decision point: a documented starting position, an agreed future state, validated data and proof that services can operate after cutover. ### 1. Understand Your Current Estate Before Designing the Future Discovery should explain how your service operation works, including the undocumented connections that keep it running. Inventory processes, forms, business objects, automation, reports, integrations, user groups, service levels and security rules. Assign an owner to validate each area. For example, a seemingly simple laptop request may create procurement tasks, check stock, obtain approval and update an asset record. Looking only at the request form misses most of the migration requirement. **Pathfinder Insight:** Record the purpose, owner, dependencies and usage of each configuration item. An inventory tells you what exists; a validated dependency map tells you what could break. ### 2. Align Processes Before You Design the Solution Agree the target process before deciding how to configure it. Different teams may use the same terms for different activities, or different terms for the same outcome. Resolve those differences with process owners before translating them into workflows. For example, two departments may classify an access request differently and require different approvals. Decide which differences reflect genuine business controls and which are historical habits. Standardise where it helps, but retain justified exceptions. Review [services and categories](https://pathfinderspecialists.com/pathfinder-specialists-blog/optimising-itsm-services-and-categories-best-practices) early. Their design affects routing, request journeys, reporting and ownership across the future platform. **Pathfinder Insight:** Finish workshops with an agreed process map, exception rules and a named decision-maker. Unresolved process questions should remain visible as decisions, not disappear into configuration assumptions. ### 3. Executive Sponsorship Matters More Than Most Organisations Realise Your sponsor needs to resolve cross-functional decisions and protect the capacity required for delivery. Naming a sponsor without agreeing their responsibilities leaves the project exposed when operational priorities compete with migration work. Consider a disagreement over a shared service catalogue. IT cannot decide HR confidentiality requirements, and the implementation team should not make that decision on either department's behalf. A clear escalation route keeps the programme moving while accountable owners make the call. **Pathfinder Insight:** Agree decision deadlines, escalation routes and outcome measures with your sponsor. Report unresolved decisions alongside delivery progress so a technically busy project does not conceal business uncertainty. ### 4. Don't Underestimate the Impact of Time Plan around elapsed time and people's availability, not just technical effort. Workshops, data approval, security reviews, supplier access and user acceptance testing all depend on people who also have operational responsibilities. Include contract milestones, change freezes, holidays, extraction windows and integration supplier lead times. Rehearse cutover, measure how long the activities take and leave capacity for fixes and retesting. A renewal deadline is a constraint, not evidence that the migration is ready. **Pathfinder Insight:** Define go/no-go criteria and a fallback plan before the final rehearsal. Name who can stop cutover, how the previous service will be restored and how records created during the transition will be reconciled. ### 5. Clean Your Data Before You Migrate Data cleansing should begin before the first trial load. Identify duplicates, missing owners, inactive users, obsolete configuration items and inconsistent categories. Agree the transformation rules with the people who understand what those records mean. Check more than headline ticket counts. Validate parent-child relationships, attachments, journal entries, timestamps, status mappings and links to services or assets. Preserve source identifiers so your team can trace and reconcile migrated records. For example, mapping every legacy “resolved” and “closed” value to a single target status could distort reporting or lose an important operational distinction. Test the business meaning of the mapping, not just whether the import accepts it. **Pathfinder Insight:** Set acceptance criteria for each data set. Reconcile totals, relationships and representative records, then obtain owner sign-off. A technically successful import does not prove the data is usable. ### 6. Don't Migrate Everything Just Because You Can Decide what to migrate, archive, rebuild or retire based on operational need. Moving every historical record and configuration can carry unnecessary complexity into the new environment. Separate open work, essential reference data and useful knowledge from older history. Agree retention, access, security and audit requirements with the appropriate owners. An archive is only useful if authorised people can find and interpret the information later. Review [knowledge management](https://pathfinderspecialists.com/pathfinder-specialists-blog/knowledge-management-in-itsm-the-foundation-for-ai-shift-left-success-and-better-service-delivery) as part of this exercise. Moving outdated articles into a new portal can undermine self-service and future AI-assisted answers. **Pathfinder Insight:** Include an owner, rationale and retrieval approach for every archive decision. “We might need it” should start a requirements conversation rather than automatically expand migration scope. ### 7. Test Real Business Scenarios, Not Just Configuration Acceptance testing should demonstrate complete service outcomes. Test across user roles, integrations, approvals, notifications and reporting, including the exceptions that interrupt normal processing. For a leaver request, verify that the correct manager approves it, tasks reach the right teams, access removal is tracked and the audit record is retained. Then test a missing manager, rejected approval, failed integration and reassigned task. Include access boundaries, customer separation, accessibility and service-level calculations. A ticket that looks correct to an administrator may behave differently for a requester or an external customer. **Pathfinder Insight:** Give service owners test scripts with expected outcomes and evidence requirements. Reconcile representative reports against the source environment so reporting defects do not emerge at the first service review. ### 8. Understand Integrations from Day One Integration discovery should establish the purpose, owner, data direction, authentication, frequency and failure behaviour of every connection. Do not assume an existing connector or script will transfer unchanged. For example, a monitoring integration may retry a failed request. If the replacement does not recognise repeated messages, a single alert can create duplicate incidents. Test deduplication, retries, error queues, recovery and reconciliation alongside normal transactions. During cutover, coordinate inbound email, monitoring and automated notifications. Running old and new routes together without controls can create duplicate tickets or send conflicting messages. **Pathfinder Insight:** Give each integration a named operational owner and recovery procedure. Confirm who will investigate failures after the implementation team has handed over. ### 9. Define Ownership and Governance Early Establish who owns the platform, processes, data, integrations, knowledge and reporting before go-live. These responsibilities are related but should not automatically fall to the same administrator. Agree configuration standards, change approval, release testing and documentation requirements. For shared platforms, define how departments or customers request changes and how competing priorities are resolved. Pathfinder's [ITSM consulting](https://pathfinderspecialists.com/services/itsm-consulting) connects process and governance decisions with the operational outcomes your migration needs to support. **Pathfinder Insight:** Make ownership practical. A responsibility matrix should identify who approves a category change, fixes failed imports and validates service reports, not simply list a generic “platform owner”. ### 10. Adoption Is as Important as Technology Build adoption into delivery from the beginning. Analysts, approvers, service owners and employees need different guidance because their tasks and concerns differ. Train people using their own service scenarios and explain what is changing, when and why. Give users a clear route for help. Review portal completion, reassignment, support demand and user feedback against an agreed baseline rather than judging adoption by logins alone. The reasons [employees bypass self-service](https://pathfinderspecialists.com/pathfinder-specialists-blog/why-employees-dont-use-self-service-portals-and-how-to-fix-it) are worth addressing before launch. Clearer service choices and trusted knowledge may matter more than a redesigned homepage. **Pathfinder Insight:** Involve departmental champions in design and testing, then use their feedback to refine training. Record recurring questions as improvements to the service experience, not simply evidence that users need more instructions. ## Special Considerations When Migrating from Cherwell A Cherwell migration needs a deliberate review of automation, objects, forms and accumulated customisation. Preserve the business outcome where it remains necessary; do not assume configuration has a direct equivalent in Ivanti Neurons. - **One-Steps:** document triggers, conditions, prompts, expressions, record updates and chained actions. Decide what to rebuild, simplify or retire rather than assuming automated conversion. - **Custom Business Objects:** map fields, identifiers, relationships, permissions and dependent reporting. Determine whether a standard target object can meet the requirement before creating another bespoke structure. - **Legacy Forms:** inspect conditional visibility, mandatory fields, buttons and validation. Redesign around the intended user journey instead of reproducing every historical field. - **Email Actions:** review inbound parsing, ticket matching, updates, approvals and notifications. Test forwarded messages, replies and duplicate prevention where relevant. - **Historical Customisation:** identify configurations whose original purpose or owner is unclear. Validate their usage and dependencies before deciding they are safe to remove. As an illustrative example, a leaver One-Step may update a custom record and send an email that triggers a separate task. The replacement must account for the complete chain, including permissions and failure handling, rather than reproducing only the visible button. **Pathfinder Insight:** Capture the requirement behind each Cherwell customisation. “Rebuild this One-Step” is less useful than a clear statement of the outcome, business rules, exceptions and audit evidence you need. ## Special Considerations When Migrating from ServiceNow A ServiceNow migration requires attention to application boundaries, the data model and dependencies beyond the IT service desk. Establish which capabilities are moving, which will remain and how the two environments will interact during transition. - **Scoped Applications:** inventory application-specific tables, scripts, permissions and cross-application dependencies. Agree how each business requirement will be supported after migration. - **Custom Workflows:** review flows, business rules, approval paths and scheduled activity in use. Separate essential controls from obsolete exceptions. - **CMDB Structure:** map classes, attributes, identifiers and relationships to the target model. Validate service dependencies and the ownership of discovery or authoritative sources. - **Integrations:** identify external endpoints, service accounts, middleware and any on-premises connectivity components. Confirm replacements and responsibilities rather than assuming connector parity. - **Reporting:** document calculation rules, filters, service-level calendars and historical trends. Agree how changes in definitions will be explained to report consumers. - **Legacy Complexity:** inspect overlapping custom rules and configuration that is no longer used. Retire it only after checking dependencies and obtaining approval. For example, the same “resolution time” label can conceal different pause rules, calendars or reopen behaviour. Rebuilding a dashboard without resolving those definitions can produce misleading comparisons after go-live. **Pathfinder Insight:** Keep a decision log for capability gaps and changed definitions. Stakeholders should know which differences are intentional, which require a workaround and which remain unresolved before accepting the new service. ## Plan for Hypercare and Continuous Improvement Hypercare should provide enhanced support until agreed stabilisation criteria are met. Define coverage, escalation, triage, communications and operational handover before go-live rather than choosing an arbitrary duration after problems appear. Track issues by severity, service impact and cause. Separate configuration defects, data problems, integration failures and training needs so the right owners can respond. Agree exit criteria covering critical defects, backlog, monitoring and the operational team's readiness to take responsibility. If capacity is constrained, Pathfinder's [resource augmentation](https://pathfinderspecialists.com/services/resource-augmentation) can complement internal teams with specialist delivery support and knowledge transfer. After stabilisation, maintain an improvement backlog and review service outcomes against your baseline. [Platform optimisation](https://pathfinderspecialists.com/services/platform-optimisation) should prioritise useful changes based on evidence from users and service performance. **Pathfinder Insight:** Treat administrator documentation, support procedures and knowledge transfer as delivery outputs. A migration is harder to sustain if the operating team cannot explain, maintain or safely change the configuration. ## FAQs About Migrating to Ivanti Neurons ### How long does an Ivanti Neurons migration take? There is no reliable universal timescale. Duration depends on scope, source-platform complexity, data quality, integrations, process redesign and available people. Establish a discovery-led plan covering trial loads, acceptance testing, cutover rehearsals and stabilisation before committing to a go-live date. ### Should we migrate historic incidents? Migrate historical incidents when they support a defined operational, reporting or retention requirement. Otherwise, a searchable, access-controlled archive may be more appropriate. Validate attachments, relationships and retrieval before retiring the source platform, and agree the approach with the relevant data and governance owners. ### Can multiple teams move into a single platform? Yes, a shared service management platform can support multiple teams, subject to the required capabilities and design. Agree process boundaries, permissions, confidentiality, reporting and ownership early. For MSPs, validate customer separation explicitly rather than assuming a shared platform guarantees it. ### What is the biggest migration risk? Underestimating the current estate is a major risk because hidden dependencies can affect scope, data, integrations and continuity. The most significant risk in your project depends on its circumstances. Use discovery and a maintained risk register to identify and control it rather than relying on a generic ranking. ### Is migration the right time to redesign processes? Yes, provided redesign is scoped and governed. Resolve process issues that would undermine the new platform, while deferring lower-priority changes to an improvement backlog. Pathfinder can help align the future operating model with a deliverable migration scope rather than combining every improvement into one release. ## Planning an ITSM Migration? Whether you're migrating from Cherwell, ServiceNow or another ITSM platform, Pathfinder Specialists helps organisations reduce project risk, align business processes and successfully adopt Ivanti Neurons. Our [Migration Services](https://pathfinderspecialists.com/services/ivanti-migration-services) cover assessment, planning, data strategy, delivery and transition. Our [Ivanti Professional Services](https://pathfinderspecialists.com/en/services/ivanti-neurons-consultancy) connect configuration, process alignment and longer-term platform capability. If you are looking for an Ivanti consultant in the UK or an Ivanti Neurons specialist, bring your current challenges and intended outcomes to a discovery conversation. We can help identify a practical next step. [Book a Discovery Call](https://pathfinderspecialists.com/en-gb/contact-us) ## Share this post [mailto:https%3A%2F%2Fpathfinderspecialists.com%2Fpathfinder-specialists-blog%2Fmigrating-to-ivanti-neurons-10-lessons-learned-from-cherwell-servicenow-and-other-itsm-migration-projects](mailto:https%3A%2F%2Fpathfinderspecialists.com%2Fpathfinder-specialists-blog%2Fmigrating-to-ivanti-neurons-10-lessons-learned-from-cherwell-servicenow-and-other-itsm-migration-projects) ## Keep reading ### [![IT professionals reviewing a ServiceNow vs Ivanti Neurons style ITSM platform comparison to assess service management, automation, and enterprise workflow capabilities.](https://pathfinderspecialists.com/hs-fs/hubfs/AI-Generated%20Media/Images/Diverse%20Team%20Discussing%20IT%20Service%20Platforms%20In%20Modern%20Office.png?width=1693&height=929&name=Diverse%20Team%20Discussing%20IT%20Service%20Platforms%20In%20Modern%20Office.png) IT Service Management (ITSM) ServiceNow vs Ivanti Neurons for ITSM: Which Platform Is Right for Your Organisation?](https://pathfinderspecialists.com/pathfinder-specialists-blog/servicenow-vs-ivanti-neurons-itsm-comparison) ### [![](https://pathfinderspecialists.com/hs-fs/hubfs/AI-Generated%20Media/Images/AI%20vs%20Traditional%20Business%20Workflow%20in%20Newcastle.png?width=1731&height=909&name=AI%20vs%20Traditional%20Business%20Workflow%20in%20Newcastle.png) AI for small business Newcastle SMEs Why Newcastle SMEs Can't Ignore AI Anymore (And How to Avoid Wasting Money on the Wrong Tools)](https://pathfinderspecialists.com/pathfinder-specialists-blog/why-newcastle-smes-cant-ignore-ai-anymore-business-case-first) [![Pathfinder Specialists](https://pathfinderspecialists.com/hubfs/Pathfinder%20Specialists%20Logo%20-%20Dark.png)](https://pathfinderspecialists.com/en-gb/home) Ivanti Neurons and ITSM consultancy from our base in Newcastle upon Tyne. Services - [All services](https://pathfinderspecialists.com/services) - [Ivanti Neurons consultancy](https://pathfinderspecialists.com/en/services/ivanti-neurons-consultancy) - [Ivanti migration services](https://pathfinderspecialists.com/services/ivanti-migration-services) - [ITSM consulting](https://pathfinderspecialists.com/services/itsm-consulting) - [Platform optimisation](https://pathfinderspecialists.com/services/platform-optimisation) - [Resource augmentation](https://pathfinderspecialists.com/services/resource-augmentation) - [MSP consulting](https://pathfinderspecialists.com/services/msp-consulting) Company - [Home](https://pathfinderspecialists.com/en-gb/home) - [About us](https://pathfinderspecialists.com/en-gb/about-us) - [Success stories](https://pathfinderspecialists.com/success-stories) - [Blog](https://pathfinderspecialists.com/pathfinder-specialists-blog) - [Ivanti partner](https://pathfinderspecialists.com/ivanti-partner-uk) - [Contact us](https://pathfinderspecialists.com/en-gb/contact-us) Get in touch Call [0191 535 4287](tel:+441915354287) Email [sales@pathfinderspecialists.com](mailto:sales@pathfinderspecialists.com) Visit Rotterdam House 116 Quayside Newcastle Upon Tyne NE1 3DY [Talk to our team](https://pathfinderspecialists.com/en-gb/contact-us) ![Ivanti Authorized Partner badge](https://pathfinderspecialists.com/hs-fs/hubfs/Ivanti_authorized_partner_badge_500x500.png?width=80&height=80&name=Ivanti_authorized_partner_badge_500x500.png) Ivanti Authorized Partner [What this means for you](https://pathfinderspecialists.com/ivanti-partner-uk) Registered company number 17247979 Registered in England and Wales. [View on Companies House (opens in a new tab)](https://find-and-update.company-information.service.gov.uk/company/17247979) © 2026 Pathfinder Specialists. All rights reserved. Cookie settings ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Sarah Thompson", "url" : "https://pathfinderspecialists.com/pathfinder-specialists-blog/author/sarah-thompson" }, "dateModified" : "2026-10-16T14:59:45.768Z", "datePublished" : "2026-10-16T14:59:45.000Z", "headline" : "Migrating to Ivanti Neurons: 10 Lessons Learned from Cherwell, ServiceNow and Other ITSM Migration Projects", "image" : [ "https://pathfinderspecialists.com/hubfs/hs-generated-images/Three%20Consultants%20Planning%20ITSM%20Migration%20at%20Whiteboard.webp" ], "mainEntityOfPage" : { "@id" : "https://pathfinderspecialists.com/pathfinder-specialists-blog/migrating-to-ivanti-neurons-10-lessons-learned-from-cherwell-servicenow-and-other-itsm-migration-projects", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://pathfinderspecialists.com/hubfs/Copy%20of%20Pathfinder%20Specialists%20Logo%20-%20Dark%20(2).png" } } } ```