Introduction

Engineers evaluate a new microcontroller (MCU) for many reasons. Cost, availability, power consumption, performance, new functionality or long-term platform needs can all start the process. With component lead times and pricing subject to change, selecting an MCU also means considering supply-chain reliability and product longevity. Once that evaluation begins, one of the first questions is usually which Microchip MCU is comparable to the device already in the design.

Migrating to a new MCU affects hardware, firmware and timelines. Engineers must understand device differences, required changes and how to validate the design.

This article walks through a staged migration workflow and the Microchip resources that support each stage, helping engineers evaluate alternatives while considering both technical requirements and long-term availability.

The Engineering Challenge

MCUs from different vendors and device families are rarely identical. Differences in device architecture, peripherals and software will typically require some development work, even when two devices look similar on paper. Peripheral configuration, pin assignments, initialization code, drivers or libraries may all need to be adapted.

Before comparing candidate devices, establish a baseline of what the existing application requires, including must-have requirements and opportunities for improvement:

• Memory
• Performance
• Peripherals
• Real-time behavior
• External hardware dependencies
• Firmware portability
• Device availability and product longevity

This baseline helps identify where hardware or software changes may be needed.

Beyond Technical Requirements: Supply-Chain Reliability

Unpredictable MCU lead times can disrupt purchasing, development schedules, production planning and time-to-market.

Availability improvements for individual devices may not apply across a product family. Verify supply at the exact manufacturer part number (MPN) level.

Microchip's broad MCU portfolio provides engineers with additional options when evaluating alternatives, helping reduce dependence on a single device or supplier. Combined with Microchip's commitment to product longevity and client-driven obsolescence practices, this provides a foundation for long-term design continuity.

With approximately 20,000 Microchip MCUs available within a 10-week lead time, engineers have access to a wide range of device options to consider when planning their next design or migration.

Explore available Microchip MCUs on Farnell/Newark to review current stock and lead times for specific devices

Understanding Migration Resources

Microchip provides a resource for each stage of migration, from the first device search through design review.

How the Migration Workflow Works

Step 1: Identify Candidates with the Cross Reference Tool

The Microchip Cross Reference Tool identifies comparable MCUs from an existing device using key characteristics and availability, narrowing the list for evaluation.

The important word is potential. A cross-reference result is a starting point, not a guarantee of a direct one-to-one replacement. If additional guidance is needed, Microchip/Avnet FAEs and sales teams can help evaluate device options and identify the best fit for the application.

Engineers should also consider current availability, expected lead times and long-term sourcing requirements when reviewing potential replacements.

Explore PIC32C Arm® Cortex®-based MCUs on Farnell/Newark to compare available devices and check current stock. 

Step 2: Understand the Migration Path

Once a candidate is selected, the next task is understanding what will change. For example, moving an existing Arm® Cortex®-M based application to a PIC32CM MCU may require engineers to review peripheral mapping, clock and pin configuration and adapt portions of the existing software.

Microchip’s Migration Series, available through migration documents and videos, helps engineers understand what to expect, the differences they may encounter and the resources available to support the transition.

Step 3: Adapt Software with the MPLAB AI Coding Assistant

Software adaptation is often a large part of moving from one MCU to another. The MPLAB AI Coding Assistant  is integrated into Visual Studio Code and can help engineers:

• Understand unfamiliar code
• Answer Microchip-specific development questions
• Develop or adapt software for the new device

This is useful when learning how functionality is implemented on a new MCU or working through code that needs to change during a migration. The MPLAB AI Coding Assistant video series offers additional examples and guidance on using the tool. AI does not eliminate the engineering work involved, but it can help engineers understand the new platform and move through software development more efficiently.

Step 4: Validate the Design with MicroCHECK

After selecting a device and adapting the design, validation becomes an important part of the process. MicroCHECK provides access to Microchip design-review expertise for supported Microchip products. For supported 32-bit PIC and SAM MCU designs, engineers can use the service when reviewing their implementation before moving further toward production.

Compiling firmware and placing the new MCU on a schematic do not replace hardware review and validation.

Design Considerations: Look Beyond a Direct Replacement

The closest device on paper may not always be the best fit. Migration can also be an opportunity to improve the existing product. A better-suited MCU may provide:

• Lower power consumption
• More integrated peripherals
• Additional memory
• Functionality that can help reduce system cost, remove external components or add new capabilities
• Greater flexibility in long-term sourcing and product lifecycle planning

Microchip's client-driven obsolescence policy helps engineers reduce the risk of unexpected End-of-Life (EOL) disruptions. Rather than following a fixed product lifecycle, Microchip is committed to continuing production as long as customer demand exists and manufacturing remains viable. This approach helps protect engineering investments, reduce the likelihood of forced redesigns and support products intended to remain in production for years.

For engineers developing products expected to remain in production for years, product lifecycle stability can be just as important as performance or peripheral capabilities.

Instead of asking only, “What replaces the MCU I have today?”, it can be useful to ask, “What Microchip MCU provides the best solution moving forward?”

Why This Matters to Engineers

Migration can stall during device selection, implementation, software adaptation or validation.

Supply availability and product longevity introduce additional considerations that can affect the success of a migration long after the initial development work is complete.

A staged workflow and dedicated resources give engineers a clearer path from device search through design review and long-term planning.

Key Takeaways: MCU Migration Checklist

Use this checklist to guide the migration:

1. Define your requirements – Identify memory, performance, peripheral, hardware and long-term sourcing needs before comparing devices.
2. Find potential alternatives – Use the Cross Reference Tool to shortlist MCUs for further evaluation.
3. Review availability – Check Farnell/Newark for device-level stock, lead times and purchasing options.
4. Plan your migration – Review the Migration Series documents and videos to understand potential hardware and software changes.
5. Adapt your software – Use the MPLAB AI Coding Assistant to help understand and update existing code, then review and verify the changes.
6. Validate your design – Use MicroCHECK for supported hardware designs and test the migrated firmware on the target hardware before production.

With a broad MCU portfolio, development resources and a commitment to product longevity, Microchip helps engineers evaluate alternatives while reducing migration complexity and supporting long-term design continuity.

For additional guidance on device selection or migration, contact your Microchip/Avnet FAE or sales team.

 
Some of the key products: 

PIC32CMPL10- 

pic32cmpl10 ARM Microcontrollers | Farnell® UK

PIC32 Family PIC32CM PL10 Series Microcontrollers MICROCHIP ARM Microcontrollers | Newark Electronic… 

PIC32CMSG00-

pic32cmsg00 ARM Microcontrollers | Farnell® UK

PIC32 Family PIC32CM SG00 Series Microcontrollers MICROCHIP ARM Microcontrollers | Newark Electronic… 

PIC32CZCA-

PIC32 Family PIC32CZ CA Series Microcontrollers ARM Microcontrollers | Farnell® UK

PIC32 Family PIC32CM SG00 Series Microcontrollers MICROCHIP ARM Microcontrollers | Newark Electronic…