QuickBooks to Business Central Migration
Budget: $1,000 – $3,000 USD
I am kicking off Sprint 1 of our move from QuickBooks to Microsoft Dynamics 365 Business Central and need an experienced partner to handle the technical migration and first-phase setup.
Scope of Sprint 1
We are bringing Finance, Accounts Payable, Banking, core reporting, dashboards, and role-based security into Business Central. All current transactions and balances must come across cleanly, but I do NOT want a one-for-one copy of our existing chart: some headings and account names will be adjusted on the way in.
Two-Location Naming Convention
Our company runs two physical sites. During migration every GL account, vendor, customer, and bank must gain a clear location code so that each site can be filtered independently. This also means:
• Account names revised to include the new code structure
• Group visibility rules that let staff see only their site’s data unless granted cross-site rights
• Permission sets that control read/write/edit/delete at the module level
Functional Areas Requiring Customisation
• Finance (full GL, dimensions, posting groups)
• Accounts Payable (vendors, approval workflows, document attachments)
• Banking (multiple bank accounts, auto-reconciliation rules)
Reporting & Dashboards
I need the default Business Central financial statements re-mapped to our new chart and an initial dashboard (Power BI) showing cash position, payables ageing, and location-level P&L. Standard reports as well as ad-hoc reporting is required features.
Data Quality & Security Expectations
Clean opening balances, verified against QuickBooks.
Audit of migrated user roles confirming only intended visibility and rights.
A brief hand-over guide summarising new naming rules and any custom fields created.
Please outline your approach to:
1. Extracting and transforming the QuickBooks data
2. Designing the dual-location naming convention
3. Configuring group visibility and permission sets
4. Testing and sign-off for each functional area
I am ready to start next week and will provide remote access to the current QB file plus our draft naming matrix. I have already purchased MS 365 Enterprise, TEAMS, and other MS tools, including Power Platform and Power Apps. I will purchase the necessary Business Central license as necessary and advised, upon awarding of this project to a knowledgeable and quick scale developer. Looking forward to your plan and timeline for completing this first sprint.
Scope of Sprint 1
We are bringing Finance, Accounts Payable, Banking, core reporting, dashboards, and role-based security into Business Central. All current transactions and balances must come across cleanly, but I do NOT want a one-for-one copy of our existing chart: some headings and account names will be adjusted on the way in.
Two-Location Naming Convention
Our company runs two physical sites. During migration every GL account, vendor, customer, and bank must gain a clear location code so that each site can be filtered independently. This also means:
• Account names revised to include the new code structure
• Group visibility rules that let staff see only their site’s data unless granted cross-site rights
• Permission sets that control read/write/edit/delete at the module level
Functional Areas Requiring Customisation
• Finance (full GL, dimensions, posting groups)
• Accounts Payable (vendors, approval workflows, document attachments)
• Banking (multiple bank accounts, auto-reconciliation rules)
Reporting & Dashboards
I need the default Business Central financial statements re-mapped to our new chart and an initial dashboard (Power BI) showing cash position, payables ageing, and location-level P&L. Standard reports as well as ad-hoc reporting is required features.
Data Quality & Security Expectations
Clean opening balances, verified against QuickBooks.
Audit of migrated user roles confirming only intended visibility and rights.
A brief hand-over guide summarising new naming rules and any custom fields created.
Please outline your approach to:
1. Extracting and transforming the QuickBooks data
2. Designing the dual-location naming convention
3. Configuring group visibility and permission sets
4. Testing and sign-off for each functional area
I am ready to start next week and will provide remote access to the current QB file plus our draft naming matrix. I have already purchased MS 365 Enterprise, TEAMS, and other MS tools, including Power Platform and Power Apps. I will purchase the necessary Business Central license as necessary and advised, upon awarding of this project to a knowledgeable and quick scale developer. Looking forward to your plan and timeline for completing this first sprint.