@devidr There is a point where maintaining an old Magento installation becomes more complicated than planning a controlled upgrade. I would start by documenting the current Magento version, PHP version, extensions, custom modules, payment systems, shipping services, ERP connections, customer data, order history, and integrations. Every customization should be classified as something that can be replaced, upgraded, rewritten, or removed. Extension compatibility is particularly important because an old module may have no suitable Magento 2 equivalent. The migration should also account for URL structures, metadata, redirects, indexing, analytics, checkout behavior, and historical orders. Security support is another major consideration when deciding whether continued maintenance is sensible. A proper Magento 2 upgrade service should therefore involve much more than installing a newer version. I would expect a staging environment, migration testing, integration testing, performance checks, backup procedures, and a carefully rehearsed launch plan. The amount of custom code often determines the real difficulty more than the number of products.
... Read more