Migrate from IPMP to Jira

IPMP individual practitioner records (name, email, phone, professional tier, registration status) map to Jira user accounts. We resolve by email as the dedupe key. IPMP membership tier maps to a Jira group membership (e.g., Certified Practitioner, Senior Practitioner, Fellow) for permission scoping within Jira projects. The original IPMP member ID is preserved in a custom field ipmp_member_id__c on the Jira user profile for cross-referencing.

IPMP certification credentials (credential name, issue date, expiry date, competency category, issuing body) map to structured issues in a dedicated Jira certification-tracking project. Each certification becomes an Issue of type Certification with custom fields for credential_reference, issuing_body (AAPM or COTVET), competency_area, and renewal_date. The Certification issue is linked to the practitioner Jira User Account via a custom user field so that each credential is retrievable against the right practitioner.

IPMP certifications issued under AAPM (USA) carry a different reference numbering convention from those issued under COTVET (Ghana). We create a custom Jira field issuing_body__c (single-select picklist: AAPM, COTVET, Dual) on the Certification issue type and populate it from the IPMP credential record so that each migrated certification retains its full issuing-body provenance without cross-contamination between frameworks.

IPMP examination results (exam name, attempt date, score, pass/fail status, competency assessed) map to Jira issues of type Examination in a separate assessment-results project. Each Examination issue links to the corresponding Practitioner User Account and to the Certification issue it contributed toward. We normalise the score format (percentage or letter grade) to a consistent numeric scale stored in a custom field score_percentage__c.

IPMP CPD logs are submitted in varying formats (spreadsheets, email attestations). We apply a normalisation step extracting date_completed, hours_claimed, competency_area, and evidence_reference from each submission. Normalised entries migrate as Jira issues of type CPD Entry in a CPD tracker project linked to the practitioner user account, or as structured custom fields on the practitioner profile if the customer prefers a lighter-weight model. We validate normalised entries against COTVET CPD requirements before loading.

IPMP training course records (course name, provider, completion date, hours, competency area) live in a third-party TVET-registered centre. We identify the external source, extract relevant records via CSV if available, and migrate them as Jira issues of type Training Course or as custom fields on the practitioner user profile. Each record links to the relevant practitioner and to the CPD log if the training contributes toward CPD hours.

IPMP corporate or organisational memberships are tracked separately from individual practitioner records. These map to Jira Groups (for permission scoping) with the organisation name as the group label. If the organisational member also has project teams using Jira, we map seat entitlements to Jira user count within the group's license allocation. Tier entitlements and billing cycles are preserved in group description fields pending admin confirmation.

IPMP-stored PDFs of certificates, ID documents, and academic credentials extract as file references. We migrate available file references and preserve download links where accessible. Full binary file migration (PDF content ingestion into Jira attachments) requires a separate file transfer engagement coordinated with IPMP's technical team; Jira's file attachment size limit (10 MB per file on Standard Cloud) constrains any bulk attachment migration.

IPMP membership tiers (practitioner level, seniority classification) map to Jira group memberships for permission management. We probe the IPMP membership agreement during discovery to identify tier entitlements, seat limits, and billing cycles before setting group assignments. Any tier boundaries not publicly documented are confirmed directly with IPMP's office during the discovery call.

IPMP billing records and payment histories are managed through a separate finance system. We do not migrate financial transaction history; only the membership tier and current standing status transfer to Jira. The customer's finance team retains access to historical IPMP billing records independently.