Project Scope: Full Lifecycle Migration from Dynamics GP to D365 BC
Key Responsibilities:
Legacy Mapping: Lead the migration of Master Records and transactional history (24 months of G/L activity) from Dynamics GP to D365 Business Central.
MEM Configuration: Translate GP's multi-company or segmented account structure into Binary Stream Multi-Entity Management (MEM) to maintain organizational hierarchy.
Functional Build: Configure core Financials, Banking (ACH/Positive Pay), and Payables within BC, ensuring MICR check formatting matches existing GP outputs.
Integration Support: Use SmartConnect to bridge legacy data gaps and automate ongoing transaction flows.
UAT & Training: Guide users through the "GP to BC" learning curve, focusing on the shift from a traditional COA to a Dimensional-based accounting model.
Required Qualifications:
Migration Expertise: Demonstrated experience leading at least two Dynamics GP to D365 BC migrations.
Technical Mastery: Deep functional knowledge of Binary Stream MEM is mandatory.
Tooling: Proficiency with eOne SmartConnect for data migration and ongoing integrations.
Clinical/Multi-Site Background: Experience in healthcare or multi-entity service environments is highly preferred.
Required D365 BC Module Expertise:
Core Financials: General Ledger, Dimensions, & Financial Reporting (Account Schedules).
Cash Management: Bank Account Reconciliation, Payment Reconciliation Journals, Positive Pay.
Accounts Receivable: Sales & Receivables and Customer Management.
Multi-Entity Management (MEM): Binary Stream (Mandatory experience for managing multiple legal entities in one tenant).
Administration: User Management, Security Groups, & Permissions.
Technical & Migration Toolset:
Migration: Dynamics GP to D365 BC Conversion (Data Mapping & COA Dimensionality).
Integration: eOne SmartConnect (for GL, Sales, Bank, and AP transaction automation).
Reporting: Solver (preferred) and standard BC Document Reporting (Sales Invoices/Checks).
MS D365 BC Migration Consultant (GP to BC)
4-5 months project
Remote + Travel
Project Scope: Full Lifecycle Migration from Dynamics GP to D365 BC
Key Responsibilities:
Legacy Mapping: Lead the migration of Master Records and transactional history (24 months of G/L activity) from Dynamics GP to D365 Business Central.
MEM Configuration: Translate GP's multi-company or segmented account structure into Binary Stream Multi-Entity Management (MEM) to maintain organizational hierarchy.
Functional Build: Configure core Financials, Banking (ACH/Positive Pay), and Payables within BC, ensuring MICR check formatting matches existing GP outputs.
Integration Support: Use SmartConnect to bridge legacy data gaps and automate ongoing transaction flows.
UAT & Training: Guide users through the "GP to BC" learning curve, focusing on the shift from a traditional COA to a Dimensional-based accounting model.
Required Qualifications:
Migration Expertise: Demonstrated experience leading at least two Dynamics GP to D365 BC migrations.
Technical Mastery: Deep functional knowledge of Binary Stream MEM is mandatory.
Tooling: Proficiency with eOne SmartConnect for data migration and ongoing integrations.
Clinical/Multi-Site Background: Experience in healthcare or multi-entity service environments is highly preferred.
Required D365 BC Module Expertise:
Core Financials: General Ledger, Dimensions, & Financial Reporting (Account Schedules).
Cash Management: Bank Account Reconciliation, Payment Reconciliation Journals, Positive Pay.
Accounts Receivable: Sales & Receivables and Customer Management.
Multi-Entity Management (MEM): Binary Stream (Mandatory experience for managing multiple legal entities in one tenant).
Administration: User Management, Security Groups, & Permissions.
Technical & Migration Toolset:
Migration: Dynamics GP to D365 BC Conversion (Data Mapping & COA Dimensionality).
Integration: eOne SmartConnect (for GL, Sales, Bank, and AP transaction automation).
Reporting: Solver (preferred) and standard BC Document Reporting (Sales Invoices/Checks).
What You'll Do
Legacy Mapping: Lead the migration of Master Records and transactional history (24 months of G/L activity) from Dynamics GP to D365 Business Central.
MEM Configuration: Translate GP's multi-company or segmented account structure into Binary Stream Multi-Entity Management (MEM) to maintain organizational hierarchy.
Functional Build: Configure core Financials, Banking (ACH/Positive Pay), and Payables within BC, ensuring MICR check formatting matches existing GP outputs.
Integration Support: Use SmartConnect to bridge legacy data gaps and automate ongoing transaction flows.
UAT & Training: Guide users through the "GP to BC" learning curve, focusing on the shift from a traditional COA to a Dimensional-based accounting model.
Migration Expertise: Demonstrated experience leading at least two Dynamics GP to D365 BC migrations.
