The migration strategy
A controlled migration starts by understanding how the current system actually supports municipal operations before designing the future state.
1. Current state
Dynamics GP often sits at the centre of municipal finance, payroll, reporting, tax, utility, and approval workflows — with add-ons, spreadsheets, GIS, document systems, and manual processes around it.
2. Migration risk
Risk increases when reports, integrations, data ownership, approval paths, blackout periods, and user adoption needs are not mapped before implementation.
3. Migration path
PCL maps workflows, data, integrations, reports, roles, controls, and cutover risks before migration begins.
4. Future state
Municipal teams operate in a more connected environment across finance, workforce, revenue, reporting, and resident-facing workflows with stronger visibility and operational control.
The municipal stack behind the migration
Dynamics GP migration is rarely only about the ERP. Municipalities often rely on a wider operating stack that includes budgeting workbooks, reporting tools, GIS, property systems, meter reads, document management, inventory systems, and department-specific workflows.
GP migration is also a PSAB readiness issue
For municipal finance teams, replacing Dynamics GP is not only a technology decision. It is also a chance to improve fund accounting, chart of accounts structure, TCA tracking, deferred revenue, grants, reserves, reporting continuity, and audit evidence before the next year-end cycle.
Chart of accounts and fund structure
Map GP segments, departments, funds, projects, and reporting dimensions into a future-state fund accounting model.
Fixed assets and TCA
Review GP fixed asset records, asset classes, useful lives, amortization schedules, and PSAB 3150 readiness.
Management Reporter and Excel schedules
Identify financial statements, budget reports, year-end schedules, and spreadsheets that need reporting continuity.
Deferred revenue, grants, and reserves
Map balances, recognition workflows, supporting documentation, and reporting responsibilities before cutover.
Migration areas that need to be mapped
A successful migration depends on understanding the workflows, data, approvals, reports, and integrations behind each operating area.
1. Finance and reconciliation
GL, AP, AR, cash, bank reconciliation, approvals, reporting, and audit support.
2. Budgeting and forecasting
Budget workflows, Excel dependencies, reporting extracts, project costing, and forecasting.
3. Tax and utilities
Taxation, utility billing, meter reads, payments, arrears, notices, and resident/ratepayer visibility.
4. Payroll and time
Payroll, time and attendance, job costing, seasonal staffing, and departmental labour allocation.
5. Assets and inventory
Fixed assets, inventory, water/fuel inventory, equipment, and operational stock dependencies.
6. Property and GIS
Property records, mapping, spatial lookup, assessment/property data, and service-location visibility.
7. Documents and reporting
Document management, report generation, audit support, and Management Reporter replacement planning.
Specialized data and workflow dependencies
Dynamics GP migration often includes more than financial data. Municipalities may need to map municipal add-ons, Excel budgeting, legacy reports, GIS records, meter reads, document systems, inventory tools, project costing, gravel haul, cemetery records, banking files, and citizen-service workflows before cutover.
Municipal add-ons and side systems
Identify which legacy extensions, add-ons, and workarounds support daily operations.
Excel and legacy reporting
Map budget workbooks, report outputs, Management Reporter, Report Designer, and spreadsheet dependencies.
GIS, meter reads, and documents
Plan handoffs with GIS, assessment, meter-read, document, and records systems.
Inventory, projects, and field operations
Review inventory, fuel/water tracking, project costing, gravel haul, and field-operation workflows.
Banking and payment files
Map EFT, direct deposit, PAD, tax and utility payment plans, and reconciliation needs.
Beyond Dynamics GP: mapping the full legacy ecosystem
Legacy ERP migration is rarely limited to one system. Municipal and county environments often include budgeting tools, payroll and time systems, job-costing applications, housing or care systems, asset tools, payment channels, GIS, departmental billing feeds, spreadsheets, and reporting tools. PCL helps map these dependencies before migration so finance, payroll, procurement, assets, reporting, and operations are not treated as disconnected workstreams.
Budgeting and reporting tools
Budget platforms, management reports, spreadsheets, exports, and department-level reporting dependencies.
Payroll, time, and job-costing systems
Employee-level payroll data, time entries, costing allocations, retro adjustments, and reconciliation needs.
Housing, care, or departmental systems
External billing feeds, program or property-level activity, service records, and summarized financial handoffs.
Asset, GIS, and field systems
Asset records, work orders, GIS references, meter reads, field activity, and infrastructure data.
Payment and procurement channels
Payment processors, P-cards, supplier records, requisitions, purchase orders, and commitment data.
What a modern municipal platform creates the foundation for
The future state is not only a new ERP. It is a more connected operating environment across finance, workforce, revenue, reporting, and service workflows.
Finance and reporting
Cleaner financial controls, reporting visibility, approvals, reconciliation, and budget confidence.
Payroll and workforce administration
More connected payroll, time-entry, employee-service, and workforce workflows.
Revenue administration
Better continuity across tax, utility billing, payments, arrears, notices, and reporting.
Operational integration
A stronger foundation for GIS, payments, identity, assessment, records, meter reads, documents, and reporting integrations.
Resident-facing service
Cleaner handoffs between back-office workflows and resident-facing access, status, and service processes.
A practical path from Dynamics GP to a modern municipal ERP environment
Migration is not just a software change. It is a workflow, data, reporting, integration, and adoption change. PCL's role is to support you through every layer.
Step 1 — Assess
Review Dynamics GP usage, workflow dependencies, reports, integrations, data quality, user roles, and operational risk.
Step 2 — Map
Define future-state workflows across finance, payroll, tax, utilities, permitting, reporting, and resident service.
Step 3 — Migrate
Extract, cleanse, convert, test-load, reconcile, validate, and sign off data before cutover.
Step 4 — Integrate
Connect the future-state environment with GIS, payments, identity, reporting, assessment, records, meter-read, and service systems.
Step 5 — Validate
Run UAT, parallel checks, report validation, role-based training, and go-live readiness reviews.
Step 6 — Stabilize
Support teams through hypercare, issue triage, reporting checks, and adoption support.
Note: Migration planning should account for finance close, payroll, taxation, utility billing, reporting, and other municipal blackout periods.