ERPNext Customization and Data Migration
Budget: $750 – $1,500 USD
Phase 0 — Foundation: Configuration of the overarching Company tree (CIS Group, CIS Integration, Hiperdist, Joint Ventures, UniBuild). Establishment of roles including "Sales User – Distribution," "Sales User – Integration," "Sales Cluster Manager," and "BU Manager." Import of the top ~80% hardware/software SKUs and the 9 core service categories. Set up multi-currency price lists, taxes, and territory segments.
● Phase 1 — Customer & Partner Master: Aggregation and import of all global active, dormant, and historical customer and partner records. Mapping partners as specifi c customer groups (Partner/Reseller) to handle back-to-back distribution paperwork smoothly. Implementation of data quality queues.
● Phase 2 — Deal Registration (The Funnel Convergence): Implementation of the dual-funnel strategy on a single Opportunity view. Configuration of distinct statuses, probability weightings, and mandated fi elds (funnel_type, partner, end_customer, vendor/product line) based on the chosen motion. 6
● Phase 3 — Quotation & B2B Operations: Enforcing strict quote generation from Opportunities. Confi guration of complex document outputs (letterheads, terms) specifi c to the issuing BU, along with multi-level discount/approval workfl ows.
● Phase 4 — Visibility & Management: Delivery of custom Executive and Cluster Manager dashboards. Surfacing KPIs such as pipeline by BU/Company, win rates by vendor line, MTD performance, and standing data-cleansing queues.
3.2 Technical Scope: Integration and Customization
The Unified ERPNext Opportunity Schema Mapping
Customize the standard ERPNext Opportunity doctype to ingest both sales matrices seamlessly. The design uses conditional visibility fields (depends_on) driven by the core funnel_type selection field:
Legacy Spreadsheet Field Source
Target ERPNext Field / Mapping Strategy
Technical Behavior & Validation Logic
Entity Name (e.g., CIS Nigeria)
company (Link Field)
Mandatory. Tied directly to the centralized Company Tree setup in Phase 0.
Account Name / Partner Company
party_name (Link to Customer Doctype)
For Integration: Maps to direct the client. For Distribution: Maps to Partner/Reseller Customer record.
Project Name / Deal Name
opportunity_title (Data Field)
Standardized indexing string for clear searching across dashboards.
Account Manager
opportunity_owner (Link to User)
Maintains strict accountability; drives the baseline row-level user security permissions.
Opportunity Description / Comments
description (Text Editor)
Captures deal metadata, support timelines, contract numbers, and execution status updates.
Business Sector
custom_business_sector (Select
Pre-populated dropdown mapping core industries (e.g., Telco, FSI, 7
Dropdown)
Public Sector).
Expected Sales Revenue / Booking Month
custom_expected_booking_window (Select Dropdown)
Standardized forecasting bucketing (e.g., Q1CY2026, September, October).
Status / Deal Stage
status (Select Dropdown)
Maps legacy values (Commit, Upside) into system-validated tracking states.
Winning %
probability (Percent Field)
Client script enforced: "Commit" auto-sets to 100%; open funnels default to 0% or custom rules.
Brand / Vendor Line
custom_brand (Link Field to Item Group / Brand)
Captures multi-vendor product lines (e.g., HP, Oracle, Huawei, NetApp, Dell, Cisco).
Deal Type / Architecture
custom_architecture_type (Select Dropdown)
Captures technology stack segments (e.g., Hardware, Software, Services, Server & Storage).
End User
custom_end_user (Link Field / Data Field)
Mandatory for Distribution deals; hidden via conditional logic for direct Integration entries.
Total Amount $ / Currency
opportunity_amount & currency (Currency Field)
Natively accepts native transactional currency values ($, €, ₦) and computes exchange rates automatically.
Payment Terms
payment_terms_template (Link Field)
Maps standardized business templates (e.g., Remdoc at sight, LC confirmed, Net 30).
3.3 Business Process Flow Diagram Disclaimer: This process flow has been designed based on our preliminary research and understanding of the business, and should be considered as an assumed workflow. The final process may vary depending on detailed requirements, operational nuances, 8
and system constraints identified during the discovery phase. We will review, validate, and refi ne this flow collaboratively and incorporate all necessary changes to ensure it accurately aligns with your actual business processes.
● Data Migration Scripts:
○ Python data migration scripts via the Frappe API to securely process legacy data from regional spreadsheets. The script ingestion parameters explicitly map to the provided data realities.
○ Rows lacking complete mandatory attributes will be automatically tagged with a custom status fi eld: data_status: Needs Review. This approach preserves historical context while routing unverified rows directly to dashboard data-cleansing queues for ongoing internal verification.
● Sprint Review Reports: Bi-weekly reports detailing the progress of configuration against the project timeline.
4.3 Phase III: Validation and Readiness
● User Acceptance Test (UAT) Plan: A detailed script of test cases for CIS Integration users to execute.
● UAT Issue Log: A tracked registry of bugs or usability issues discovered during testing, along with their resolution status.
● Training Library: A suite of educational materials, including recorded training sessions and role-specific user manuals.
11
4.4 Phase IV: Go-Live and Closure
● Production Environment: The live, transaction-ready ERPNext instance populated with final master data and opening inventory balances.
● Project Closure Report: A summary of the project’s performance against budget and timeline, including a roadmap for future phases.
● Phase 1 — Customer & Partner Master: Aggregation and import of all global active, dormant, and historical customer and partner records. Mapping partners as specifi c customer groups (Partner/Reseller) to handle back-to-back distribution paperwork smoothly. Implementation of data quality queues.
● Phase 2 — Deal Registration (The Funnel Convergence): Implementation of the dual-funnel strategy on a single Opportunity view. Configuration of distinct statuses, probability weightings, and mandated fi elds (funnel_type, partner, end_customer, vendor/product line) based on the chosen motion. 6
● Phase 3 — Quotation & B2B Operations: Enforcing strict quote generation from Opportunities. Confi guration of complex document outputs (letterheads, terms) specifi c to the issuing BU, along with multi-level discount/approval workfl ows.
● Phase 4 — Visibility & Management: Delivery of custom Executive and Cluster Manager dashboards. Surfacing KPIs such as pipeline by BU/Company, win rates by vendor line, MTD performance, and standing data-cleansing queues.
3.2 Technical Scope: Integration and Customization
The Unified ERPNext Opportunity Schema Mapping
Customize the standard ERPNext Opportunity doctype to ingest both sales matrices seamlessly. The design uses conditional visibility fields (depends_on) driven by the core funnel_type selection field:
Legacy Spreadsheet Field Source
Target ERPNext Field / Mapping Strategy
Technical Behavior & Validation Logic
Entity Name (e.g., CIS Nigeria)
company (Link Field)
Mandatory. Tied directly to the centralized Company Tree setup in Phase 0.
Account Name / Partner Company
party_name (Link to Customer Doctype)
For Integration: Maps to direct the client. For Distribution: Maps to Partner/Reseller Customer record.
Project Name / Deal Name
opportunity_title (Data Field)
Standardized indexing string for clear searching across dashboards.
Account Manager
opportunity_owner (Link to User)
Maintains strict accountability; drives the baseline row-level user security permissions.
Opportunity Description / Comments
description (Text Editor)
Captures deal metadata, support timelines, contract numbers, and execution status updates.
Business Sector
custom_business_sector (Select
Pre-populated dropdown mapping core industries (e.g., Telco, FSI, 7
Dropdown)
Public Sector).
Expected Sales Revenue / Booking Month
custom_expected_booking_window (Select Dropdown)
Standardized forecasting bucketing (e.g., Q1CY2026, September, October).
Status / Deal Stage
status (Select Dropdown)
Maps legacy values (Commit, Upside) into system-validated tracking states.
Winning %
probability (Percent Field)
Client script enforced: "Commit" auto-sets to 100%; open funnels default to 0% or custom rules.
Brand / Vendor Line
custom_brand (Link Field to Item Group / Brand)
Captures multi-vendor product lines (e.g., HP, Oracle, Huawei, NetApp, Dell, Cisco).
Deal Type / Architecture
custom_architecture_type (Select Dropdown)
Captures technology stack segments (e.g., Hardware, Software, Services, Server & Storage).
End User
custom_end_user (Link Field / Data Field)
Mandatory for Distribution deals; hidden via conditional logic for direct Integration entries.
Total Amount $ / Currency
opportunity_amount & currency (Currency Field)
Natively accepts native transactional currency values ($, €, ₦) and computes exchange rates automatically.
Payment Terms
payment_terms_template (Link Field)
Maps standardized business templates (e.g., Remdoc at sight, LC confirmed, Net 30).
3.3 Business Process Flow Diagram Disclaimer: This process flow has been designed based on our preliminary research and understanding of the business, and should be considered as an assumed workflow. The final process may vary depending on detailed requirements, operational nuances, 8
and system constraints identified during the discovery phase. We will review, validate, and refi ne this flow collaboratively and incorporate all necessary changes to ensure it accurately aligns with your actual business processes.
● Data Migration Scripts:
○ Python data migration scripts via the Frappe API to securely process legacy data from regional spreadsheets. The script ingestion parameters explicitly map to the provided data realities.
○ Rows lacking complete mandatory attributes will be automatically tagged with a custom status fi eld: data_status: Needs Review. This approach preserves historical context while routing unverified rows directly to dashboard data-cleansing queues for ongoing internal verification.
● Sprint Review Reports: Bi-weekly reports detailing the progress of configuration against the project timeline.
4.3 Phase III: Validation and Readiness
● User Acceptance Test (UAT) Plan: A detailed script of test cases for CIS Integration users to execute.
● UAT Issue Log: A tracked registry of bugs or usability issues discovered during testing, along with their resolution status.
● Training Library: A suite of educational materials, including recorded training sessions and role-specific user manuals.
11
4.4 Phase IV: Go-Live and Closure
● Production Environment: The live, transaction-ready ERPNext instance populated with final master data and opening inventory balances.
● Project Closure Report: A summary of the project’s performance against budget and timeline, including a roadmap for future phases.