Migration from Next CRM to Frappe CRM

[nitun]

When these two tasks are finished

• ERPNext <> Frappe CRM Integration Bridge App #382
• Build Extension/Features App #383

Work on the migration of all the data into Frappe CRM and the respective extension/featured doctypes and field.

Acceptance Criteria:

• Analyze existing data structure and inconsistencies.
• Reports data generated correctly.
• Record counts match
• logs, notes, custom data → Stage change logs, status change logs, CRM Notes, attachments, opportunity status checklists.

[nitun]

• Custom fields - Next CRM ships 54 custom fields with module = "NCRM". The bridge ships ~11 with module = "Next CRM Bridge". Some fields overlap and just need re-attribution.
• Status field type - Next CRM keeps Lead.status as a Select field with hardcoded values; the bridge converts it to a Link → CRM Lead Status. Frappe's rename-cascade handles the data, but every existing status value must exist as a row in CRM Lead Status before the conversion runs, or rows fail validation. Same applies to Opportunity.sales_stage if the bridge converts that too.
• Status / Stage Change Log child tables - Next CRM has two child tables on Opportunity (status_change_log, custom_stage_change_log); the bridge consolidates them into a single status_change_log child of type CRM Status Change Log. A patch needs to merge the rows and tag them with type=status vs type=stage.
• FCRM Note custom fields - Next CRM added custom_title, custom_parent_note, custom_note_attachments. The bridge uses the upstream FCRM Note as-is (which has a title natively but no parent_note or custom attachments table). A patch copies custom_title → title, migrates note attachments into Frappe core File records linked to the note, and either drops parent_note
• Custom doctypes - Next CRM's Opportunity Status Checklist → what to do with this?

@dpk404 please verify these things are done or pending? Also, add if anything is missing.