Project Management migration
Field-level mapping, validation, and rollback between IPMP and Microsoft Project. We move data and schema; workflows are rebuilt natively in Microsoft Project.
IPMP
Source
Microsoft Project
Destination
Compatibility
7 of 10
objects map 1:1 between IPMP and Microsoft Project.
Complexity
BStandard
Timeline
2-4 weeks
Overview
IPMP is a professional certifying institution and membership body under Ghana's Companies Code 1963, not a project management software platform. The migration from IPMP to Microsoft Project is a credential-data migration rather than a like-for-like software migration: member profiles, certification histories, professional examination results, and continuing professional development records move into Microsoft Project as resources, custom fields, and project-linked metadata. There is no confirmed public API for IPMP's membership system; export relies on CSV extracts from the admin portal or direct database access coordinated with the institute. We normalise CPD entries that arrive in inconsistent formats (spreadsheets, email attestations) before loading, preserve the dual AAPM and COTVET issuing-body codes on each certification record, and map organisational membership tiers to Planner Premium resource role data. Workflows, automations, and reporting configurations do not migrate; we deliver a written inventory of these for your admin to rebuild in the destination system.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a IPMP object lands in Microsoft Project, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
IPMP
Members
Microsoft Project
Resource (Planner Premium) or User (Project Online)
1:1IPMP individual member records (name, email, phone, professional tier, registration status against Companies Code Act 179) map to Planner Premium Resource records or Project Online Resource records. The member's IPMP tier (Graduate, Member, Fellow) maps to a Resource custom field ipmp_tier__c. Email becomes the primary lookup key. If a member has an active Microsoft 365 account matching the email, they become a Bookable Resource; otherwise they are mapped as a Generic Resource. We resolve the mapping during the discovery call with the IPMP admin export.
IPMP
Certifications
Microsoft Project
Custom fields on Resource and/or Project
lossyIPMP certification records (AAPM-issued and COTVET-issued) have no native Microsoft Project equivalent. We create custom fields on the Resource record: ipmp_certification_body__c (AAPM or COTVET), ipmp_cert_issue_date__c, ipmp_cert_expiry_date__c, ipmp_competency_area__c, and ipmp_cert_reference__c to preserve the issuing body code. If the customer uses Planner Premium, certification fields live on the Resource; if Project Online with PWA, they live as enterprise custom fields on the Resource entity. We maintain the dual-framework mapping table so that each credential retains its full provenance.
IPMP
Professional Examinations
Microsoft Project
Task (custom project) or custom fields on Resource
1:1Examination results (scores, attempt dates, pass/fail status, competency area) are mapped as records in a dedicated Planner project called 'IPMP Certification Records' or as custom fields on each Resource. If the source data lives in a separate assessment platform integrated via API, we identify the external source, extract records by member email, and re-associate each result with the corresponding Resource in the destination. Pass/fail status becomes a boolean custom field ipmp_exam_passed__c with the score stored as ipmp_exam_score__c.
IPMP
Continuing Professional Development (CPD) Logs
Microsoft Project
Task records in a CPD project or Planner bucket
lossyCPD hours are logged in varying formats across IPMP members (spreadsheets, email attestations). We apply a normalisation step extracting date, hours claimed, competency area, and evidence reference before loading into Microsoft Project. Each CPD entry becomes a Task in a dedicated 'CPD Tracking' Planner plan or Project Online project, linked to the member's Resource record via the Assignee field. The task name captures the competency area; hours claimed map to a custom numeric field cpd_hours__c. We validate normalised entries against COTVET CPD requirements (minimum hours per renewal period) and flag any gaps in the reconciliation report.
IPMP
Training Courses
Microsoft Project
Task or Milestone in a training project
1:1Course completion records sourced from IPMP's third-party TVET-registered centre map to Task records in a 'IPMP Training History' Planner project. Each course becomes a Task with start and end dates, completion status, and the delivering institution stored as a custom field. We identify the external LMS source during discovery and extract relevant records before associating them with the corresponding member Resource. If the TVET centre uses a separate system with no export capability, we flag the gap and note the manual-entry requirement.
IPMP
Organisational Members
Microsoft Project
Department or custom group in Planner / Resource custom field
lossyCorporate or organisational memberships tracked separately from individual practitioner records have no direct Planner or Project Online equivalent. We map organisational members as a custom text field org_member_name__c on each individual member Resource, or as a Planner Group with the organisational name. Tier entitlements, seat limits, and billing cycles from the membership agreement are captured in a separate lookup table provided to the customer's admin for manual configuration in Planner governance settings. This mapping requires the IPMP membership agreement during discovery.
IPMP
Document Storage
Microsoft Project
SharePoint document library linked to Planner project
1:1Certificates, ID documents, and academic credentials stored as PDFs or scanned images in IPMP's document system are referenced by file name and path in the migration export. We extract available file references, preserve the original issuing body and certificate number embedded in filenames, and document them in a SharePoint document library within the customer's Microsoft 365 environment. Full file migration requires a separate file-transfer step coordinated with IPMP's technical team; document URLs in the destination point to the new SharePoint location.
IPMP
Invoices and Payments
Microsoft Project
Not migrated (flagged for admin reference)
1:1Billing records and payment histories are managed through a separate finance system in IPMP and are not migrated to Microsoft Project. We confirm the finance system during discovery and note its existence in the migration handoff document. The membership tier and current standing (Active, Lapsed, Suspended) are the only financial-adjacent fields transferred to the destination, mapped as a Resource custom field ipmp_membership_status__c.
IPMP
Membership Tier
Microsoft Project
Custom picklist field on Resource
1:1IPMP membership tiers (Graduate, Member, Fellow, Corporate) map to a Planner Premium Resource custom picklist field ipmp_membership_tier__c. The tier assignment determines which Planner plans or project folders the member can access, managed through Microsoft 365 group membership post-migration. We probe the membership agreement during discovery to confirm the full tier hierarchy and any tier-gated access rules that need to be replicated in Planner governance.
IPMP
COTVET Renewal Status
Microsoft Project
Custom date and status fields on Resource
1:1The COTVET continuing professional development renewal cycle (renewal date, CPD hours required, hours completed to date) is a time-sensitive record that maps to two custom fields on each Resource: cpd_renewal_due_date__c and cpd_hours_required__c. These fields are used by the customer's admin to set Power Automate reminders for renewal deadlines. We compute the renewal date from the original certification issue date and COTVET's renewal period policy, and validate that the CPD hours claimed in the normalised CPD tasks satisfy the requirement.
| IPMP | Microsoft Project | Compatibility | |
|---|---|---|---|
| Members | Resource (Planner Premium) or User (Project Online)1:1 | Mapping required | |
| Certifications | Custom fields on Resource and/or Projectlossy | Mapping required | |
| Professional Examinations | Task (custom project) or custom fields on Resource1:1 | Mapping required | |
| Continuing Professional Development (CPD) Logs | Task records in a CPD project or Planner bucketlossy | Mapping required | |
| Training Courses | Task or Milestone in a training project1:1 | Mapping required | |
| Organisational Members | Department or custom group in Planner / Resource custom fieldlossy | Mapping required | |
| Document Storage | SharePoint document library linked to Planner project1:1 | Mapping required | |
| Invoices and Payments | Not migrated (flagged for admin reference)1:1 | Not supported | |
| Membership Tier | Custom picklist field on Resource1:1 | Fully supported | |
| COTVET Renewal Status | Custom date and status fields on Resource1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
IPMP gotchas
No public API confirmed for automated data export
Certification records span multiple issuing bodies
CPD logging is unstructured and varies by member
Organisational membership tier boundaries are not publicly documented
Microsoft Project gotchas
Project for the web is being retired and merged into Microsoft Planner
Planner-tier portfolio features are incomplete despite Plan 5 labeling
Web app constraint controls are weaker than the Windows desktop client
Project requires a separate license not bundled with standard Microsoft 365
Project Online API is edition-gated and inconsistently documented
Pair-specific challenges
Migration approach
Discovery and export capability confirmation
We conduct a scoping call with the IPMP institution and the migrating organisation to confirm the export mechanism available from IPMP's membership system. We inventory all member records, certification records, examination results, CPD logs, training completions, and document references in scope. We identify whether IPMP can provide a CSV export from the admin portal, a direct database query, or only paper certificates for some records. We also confirm the target Microsoft Project destination: Planner Premium (web app, integrated with Microsoft 365) or Project Online with PWA. This step produces a written migration scope and a data dictionary for the IPMP export.
Source data assessment and CPD normalisation
We receive the IPMP data export and apply an initial quality assessment: duplicate member records, missing mandatory fields, inconsistent CPD formats, and dual-framework certification codes. For CPD logs, we run the normalisation pipeline to extract structured entries from whatever format they arrived in. We flag any records that cannot be parsed or that have missing critical fields (member email, certification date, CPD hours) and return a data quality report to the customer for resolution before migration begins. We build the issuing-body mapping table for AAPM and COTVET certification records at this stage.
Planner or Project Online destination configuration
We configure the destination environment in Planner Premium or Project Online before any data is loaded. This includes creating the Resource schema with all IPMP custom fields (ipmp_membership_tier__c, ipmp_certification_body__c, cpd_renewal_due_date__c, and others), setting up the CPD Tracking project and any additional Planner plans or PWA projects for certification and training history, configuring Microsoft 365 group membership to reflect organisational membership tiers, and applying Planner governance settings (resource booking, approval workflows) per the customer's requirements. Configuration is validated in a dedicated Planner demo plan or Project Online sandbox before production migration.
Sandbox migration and reconciliation
We run a full migration into a Planner Premium test plan or Project Online sandbox environment using production data volume. The customer's migration lead reviews a randomised sample of migrated Resources against the IPMP source records, verifies that certification dates and CPD hours are accurate, and confirms that the dual-framework certification mapping is preserved. We run a row-count reconciliation report comparing source record counts to destination record counts for each object type. Any mapping corrections are applied to the migration scripts and the sandbox migration is re-run until reconciliation passes. The customer signs off on the sandbox result before production migration begins.
Production migration in dependency order
We run production migration in record order: Resource records (from IPMP Members) first with email as the dedupe key, then certification custom fields applied to each Resource, then examination results as tasks in the certification project, then CPD entries as tasks in the CPD Tracking project, then training history as tasks, then document references added to SharePoint. Each phase emits a reconciliation report before the next begins. If IPMP is still accepting new records during the migration window, we run a final delta pass after cutover to capture any records added between the initial export and the production cutover date.
Cutover, validation, and admin rebuild handoff
We freeze IPMP writes and run a final delta migration on cutover day. We verify that all Resources have complete custom field values, that CPD tasks satisfy COTVET renewal requirements, and that organisational membership tiers are reflected in Planner group membership. We deliver a written inventory of any Planner automations, Power Automate flows, or reporting configurations that the customer's admin needs to rebuild, including CPD reminder flows tied to cpd_renewal_due_date__c and membership tier expiry alerts. We do not rebuild these automations as part of the standard migration scope. We provide a one-week post-migration support window for reconciliation issues raised by the project team.
Platform deep dives
IPMP
Source
Strengths
Weaknesses
Microsoft Project
Destination
Strengths
Weaknesses
Complexity grading
Standard Project Management migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across IPMP and Microsoft Project.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
IPMP: N/A.
Data volume sensitivity
IPMP doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during IPMP to Microsoft Project migration scoping. Not seeing yours? Book a call.
Walk through your IPMP to Microsoft Project migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave IPMP
Other ways to arrive at Microsoft Project
Same-Project Management migrations
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.