# Eclipse to Prophet 21 Migration Readiness Assessment > Source: https://netray.co/tools/eclipse-to-prophet-21-migration-readiness-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Ten questions to gauge how ready a distributor is to move between Eclipse and Prophet 21 or any similar change of distribution ERP. ## Category erp-migration ## Erp Epicor Eclipse ## Industry Wholesale Distribution ## Audience - CIO - Distribution executive - Project sponsor - ERP manager ## Tool **Kind:** assessment **Questions:** #### How clean is your item master? **Help:** Duplicates, missing units, inconsistent descriptions. **Options:** ##### Known duplicates and many gaps **Score:** 0 ##### Some cleanup done, no owner **Score:** 1 ##### Mostly clean with a named owner **Score:** 2 ##### Governed with rules and regular audits **Score:** 3 #### How well documented is your pricing (multipliers, matrices, contracts)? **Options:** ##### Lives in people's heads **Score:** 0 ##### Partly documented **Score:** 1 ##### Documented, with stale entries **Score:** 2 ##### Documented, current and reviewed **Score:** 3 #### Do you know which customizations and reports you rely on? **Options:** ##### No inventory of them **Score:** 0 ##### A partial list **Score:** 1 ##### Full list, not ranked **Score:** 2 ##### Full list ranked by use and business value **Score:** 3 #### How accurate is inventory by location today? **Options:** ##### Below 90 percent **Score:** 0 ##### About 90 to 95 percent **Score:** 1 ##### About 95 to 98 percent **Score:** 2 ##### Above 98 percent with regular counts **Score:** 3 #### Do you have an executive sponsor with time to decide? **Options:** ##### No sponsor **Score:** 0 ##### Sponsor in name only **Score:** 1 ##### Engaged but busy **Score:** 2 ##### Engaged, with weekly decision time **Score:** 3 #### Can branch and department leads give time for design and testing? **Options:** ##### No capacity **Score:** 0 ##### A few hours with difficulty **Score:** 1 ##### Planned time for key roles **Score:** 2 ##### Backfill arranged for key roles **Score:** 3 #### How many EDI, portal and e-commerce integrations must be rebuilt? **Options:** ##### Many, and undocumented **Score:** 0 ##### Many, documented **Score:** 1 ##### A few, documented **Score:** 2 ##### Few, documented with partner contacts **Score:** 3 #### How much history must be migrated? **Options:** ##### Everything, no decision **Score:** 0 ##### Several years, unclear need **Score:** 1 ##### Defined scope with archive plan **Score:** 2 ##### Minimal history plus a read-only archive **Score:** 3 #### Do you have a tested data reconciliation approach? **Options:** ##### None **Score:** 0 ##### Spot checks only **Score:** 1 ##### Defined for some areas **Score:** 2 ##### Count and value tie-outs for orders, stock, AR and AP **Score:** 3 #### How is training and change management planned? **Options:** ##### Not planned **Score:** 0 ##### A training week before go-live **Score:** 1 ##### Role-based training and super users **Score:** 2 ##### Role-based training, super users and post-go-live support **Score:** 3 **Bands:** #### Not ready **Min:** 0 **Max:** 39 **Verdict:** Major gaps in data, ownership or capacity make a migration risky now. **Recommendations:** - Name a sponsor and a data owner before choosing dates - Start item master and pricing cleanup now - Inventory customizations, reports and integrations #### Partly ready **Min:** 40 **Max:** 64 **Verdict:** Some foundations exist, but several areas could cause delay or rework. **Recommendations:** - Close the lowest-scoring areas before design starts - Rank reports and integrations by business value - Define reconciliation rules for orders, stock and receivables #### Mostly ready **Min:** 65 **Max:** 84 **Verdict:** You can plan a project, with a few risks to manage. **Recommendations:** - Fix remaining weak areas in the first phase - Plan backfill for key staff - Schedule a mock data load early #### Ready to plan **Min:** 85 **Max:** 100 **Verdict:** Your foundations are strong. Focus on scope discipline and testing. **Recommendations:** - Lock scope and resist customization creep - Run at least two mock loads and one parallel period - Keep the sponsor engaged through cutover ## Content **Intro:** Moving a distributor between Eclipse and Prophet 21, or any other distribution ERP, is mostly a data and people project. This ten-question assessment shows where readiness is thin so you can address it before spending on design. **Sections:** #### How to use the assessment **Body:** Have two or three people answer separately: IT, a branch or operations leader, and finance. Compare answers, because differences themselves reveal risk. A sponsor may believe pricing is documented while the pricing analyst knows it is not. Use the total as a conversation starter and the lowest-scoring questions as the first work items. #### What the questions cover **Body:** The questions test five areas: item and pricing data, inventory accuracy, customizations and integrations, people and sponsorship, and the plan for history, reconciliation and training. These are the areas where distributor projects most often slip, because they depend on business time more than on software configuration. **Bullets:** - Data: item master, pricing, history scope - Operations: inventory accuracy by location - Technology: customizations, reports, EDI, portals - People: sponsor, branch time, training #### Different products, different shape **Body:** Eclipse and Prophet 21 are different products with different data models, pricing structures and terminology, so a move is a re-implementation, not an upgrade. Treat every Eclipse concept as something to map rather than something that carries over. Even moving within the same vendor family, expect to re-decide pricing, security roles and reports. #### Common mistakes **Body:** Frequent causes of overruns are migrating all history without a need, rebuilding every old report instead of retiring unused ones, loading dirty item data and fixing it afterward, and underestimating branch staff time. A short readiness check helps surface each one early. **Cta:** If your score shows gaps in data or reporting, we can discuss a read-only review of your current system data and a plan for the cleanup. **Faq:** #### Is moving from Eclipse to Prophet 21 an upgrade? **Answer:** No. They are different Epicor products with different structures, so the move is a new implementation with data conversion. Plan design workshops, mapping, testing and training as for any ERP change. #### How much history should we migrate? **Answer:** Usually the minimum that people use daily: open orders, current balances, item and customer masters, and recent history for pricing and demand. Keep older history in a read-only archive you can query. #### How long does a migration take? **Answer:** It depends on branch count, integrations and data quality. Many distributor projects take from several months to more than a year. A readiness review replaces guesswork with the actual risks. #### Does a low score mean we should not migrate? **Answer:** No. It means prepare first. Item cleanup, pricing documentation and a named sponsor are inexpensive steps that shorten the later project and lower the chance of rework. ## Search terms eclipse to prophet 21 migration, epicor eclipse migration readiness, distribution erp migration assessment, erp readiness assessment distributor, p21 implementation readiness, erp data migration readiness, epicor eclipse replacement, distribution erp change management --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json