Version: 1.0.0 (Outline)Documentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
Last Updated: 2025-11-26
Target Audience: Implementation Team, Data Migration Specialists, CFO/Controller
1. Overview
This guide outlines the strategy, tools, and processes for migrating financial data from Microsoft Dynamics 365 Business Central to the Encore Health OS FA (Finance & Accounting) module.1.1 Migration Scope
Data to Migrate:- Chart of Accounts (Account Master)
- Fiscal Year and Period Definitions
- General Ledger (Historical Balances)
- Vendor Master and Open Payables
- Customer Master and Open Receivables
- Open Purchase Orders (if applicable)
- Budget Data (if applicable)
- Closed transactions older than 7 years (per retention policy)
- Draft/cancelled transactions
- System audit logs (start fresh in Encore Health OS)
1.2 Migration Phases
| Phase | Timeline | Description |
|---|---|---|
| Phase 1: Planning | Week 1-2 | Data assessment, mapping, resource allocation |
| Phase 2: Setup | Week 3-4 | Configure Encore Health OS FA, create CoA, define funds/departments |
| Phase 3: Data Extraction | Week 5 | Export data from D365 BC via SQL/Excel |
| Phase 4: Transformation | Week 6-7 | Map D365 fields to Encore Health OS schema, cleanse data |
| Phase 5: Load & Validate | Week 8-9 | Import data to Encore Health OS, validate balances |
| Phase 6: Parallel Run | Week 10-11 | Run both systems in parallel, reconcile daily |
| Phase 7: Cutover | Week 12 | Go-live on Encore Health OS, freeze D365 BC |
| Phase 8: Post-Cutover Support | Week 13-16 | Monitor, troubleshoot, user training |
2. Chart of Accounts Mapping
2.1 D365 BC Structure
D365 Business Central uses a flat account structure:2.2 Encore Health OS FA Structure
Encore Health OS uses fund accounting with multi-dimensional tracking:2.3 Mapping Strategy
Step 1: Export D365 CoA| D365 BC Account Type | Encore Health OS Account Type | Notes |
|---|---|---|
| Bank Account | Asset (Bank Account - Checking) | Map to cash account subtype |
| Accounts Receivable | Asset (Accounts Receivable) | |
| Fixed Assets | Asset (Fixed Assets) | |
| Accounts Payable | Liability (Accounts Payable) | |
| Long-term Liabilities | Liability (Long-term Liabilities) | |
| Equity | Equity (Net Assets) | Nonprofits use “Net Assets” instead of “Equity” |
| Revenue | Revenue | Map to appropriate revenue subtype |
| Cost of Goods Sold | Expense (Direct Program Costs) | |
| Operating Expenses | Expense (Operating Expenses) |
- Account number starts with “3xxx” (Restricted Grant Accounts) → Assign to specific grant fund
- Account name contains “Endowment” → Assign to “Permanently Restricted Fund”
- Expense accounts →
requires_department = true - Revenue accounts →
requires_program = true(for program attribution)
3. General Ledger Migration
3.1 Balance Migration (Opening Balances)
Recommended Approach: Migrate opening balances as of fiscal year start, NOT transaction-by-transaction. Step 1: Extract Trial Balance from D365 BC- Entry must balance (total debits = total credits)
- Run trial balance in Encore Health OS and compare to D365 BC trial balance
- Reconcile to penny-level accuracy
3.2 Transaction-Level Migration (Optional)
When to Use:- Regulatory requirement to maintain transaction history (e.g., grant audit trail)
- Need to drill down to original journal entries for forensic accounting
- Export ALL D365 BC journal entries for fiscal year
- Map entry types (General, Payment, Invoice, etc.) to Encore Health OS entry types
- Create journal entries in Encore Health OS with
migrated_from_d365 = trueflag - Post all entries to recreate historical balances
4. Vendor & Customer Migration
4.1 Vendor Master Migration
Step 1: Export Vendors from D365 BC4.2 Customer Master Migration
Step 1: Export Customers from D365 BC- Similar process to vendors
- Encrypt
tax_id_encryptedfield - Map payment terms to days (e.g., “NET30” → 30)
5. Open Payables & Receivables
5.1 Open Vendor Bills
Step 1: Export Open Payables from D365 BC5.2 Open Customer Invoices
Step 1: Export Open Receivables from D365 BC- Similar process to vendor bills
- Update invoice status (
sent,partial,overdue)
6. Budget Migration
6.1 D365 BC Budget Export
6.2 Encore Health OS Budget Load
7. Data Validation & Reconciliation
7.1 Validation Checklist
Pre-Migration Validation:- D365 BC trial balance balanced (debits = credits)
- All account numbers mapped to Encore Health OS accounts
- Vendor/customer counts match (D365 export vs Encore Health OS import)
- Open payables total matches D365 BC Accounts Payable balance
- Open receivables total matches D365 BC Accounts Receivable balance
- Encore Health OS trial balance matches D365 BC trial balance (by account)
- Total assets = Total liabilities + Total equity
- Cash account balance matches bank reconciliation
- Vendor aging report totals match
- Customer aging report totals match
- Budget totals match (revenue and expense)
7.2 Reconciliation Report
Generate Comparison Report:- Variance > $0.01 requires investigation
- Common causes: rounding errors, unmapped accounts, missing transactions
- Document all variances in migration log
8. Parallel Run Strategy
8.1 Parallel Run Duration
Timeline: 2-4 weeks (minimum 1 full month-end close) Process:- Week 1-2: Post all transactions in BOTH D365 BC and Encore Health OS
- Week 3-4: Reconcile daily balances between systems
- Month-End Close: Perform month-end in both systems, compare financial statements
- Go/No-Go Decision: If variance < $100 total and all reconciliations complete, proceed to cutover
8.2 Daily Reconciliation Procedure
End of Day (5:00 PM):- Print trial balance from D365 BC
- Print trial balance from Encore Health OS FA
- Compare account-by-account
- Investigate any variance > $1
- Document findings in
parallel_run_log.xlsx
- Finance team meeting every Friday at 2 PM
- Review week’s variances
- Identify process improvements
- Update user training materials
9. Cutover Plan
9.1 Cutover Timeline
Friday, 5:00 PM (Last day of parallel run):- Final reconciliation complete
- All variances documented and resolved
- CFO approval obtained
- Users notified of cutover window
- Freeze D365 BC (read-only mode)
- Post final journal entries in Encore Health OS
- Run final trial balance and financial statements
- Update DNS/URLs to point to Encore Health OS
- Send go-live notification to all users
- Users begin using Encore Health OS FA exclusively
- On-site support available for first 3 days
- Helpdesk tickets monitored hourly
9.2 Rollback Plan
Criteria for Rollback:- Critical system failure preventing GL posting
- Data corruption discovered in Encore Health OS
- Unrecoverable variance in financial statements
- Re-enable D365 BC posting
- Notify all users to revert to D365 BC
- Schedule emergency meeting with implementation team
- Analyze root cause
- Reschedule cutover after issues resolved
10. Post-Cutover Support
10.1 Support Schedule
Week 1 (Critical Support):- On-site support: 8 AM - 6 PM daily
- Helpdesk: 24/7 monitoring
- Daily check-ins with CFO and Controller
- On-site support: 8 AM - 5 PM Mon-Fri
- Helpdesk: Standard hours (8 AM - 8 PM)
- Weekly check-ins with finance team
- Helpdesk: Standard hours
- Monthly user training refreshers
- Quarterly system health review
10.2 Training Plan
Pre-Cutover Training:- 2-hour overview session for all finance staff
- Hands-on training: Journal entries and month-end close
- Hands-on training: Vendor bill processing and payments
- Hands-on training: Customer invoicing and receipts
- Hands-on training: Financial reporting
- Just-in-time training during first week
- Advanced topics (budgeting, consolidation) in month 2
- Admin training (chart of accounts maintenance) in month 2
11. Migration Tools & Scripts
11.1 SQL Export Scripts
Location:migrations/d365-export/
export_coa.sql- Chart of Accounts exportexport_trial_balance.sql- Trial balance as of cutover dateexport_vendors.sql- Vendor masterexport_customers.sql- Customer masterexport_open_payables.sql- Open vendor billsexport_open_receivables.sql- Open customer invoicesexport_budgets.sql- Budget data
11.2 Transformation Scripts
Location:migrations/transform/
transform_coa.ts- Map D365 accounts to Encore Health OS schematransform_vendors.ts- Cleanse and encrypt vendor datatransform_customers.ts- Cleanse and encrypt customer datavalidate_balances.ts- Compare D365 vs Encore Health OS balances
11.3 Data Load Scripts
Location:migrations/load/
load_accounts.ts- Bulk insert chart of accountsload_vendors.ts- Bulk insert vendorsload_customers.ts- Bulk insert customersload_opening_balances.ts- Create opening balance journal entryload_open_payables.ts- Create open vendor billsload_open_receivables.ts- Create open customer invoices
12. Known Issues & Workarounds
12.1 D365 BC Multi-Currency
Issue: Encore Health OS FA v1.0 does not support multi-currency. Workaround:- Convert all foreign currency balances to USD at cutover date exchange rate
- Document exchange rates used in migration log
- Plan for multi-currency support in Encore Health OS FA v1.1 (Q2 2026)
12.2 D365 BC Dimensions
Issue: D365 BC has 8 dimensions (Department, Program, Grant, etc.), Encore Health OS FA has 3 (Fund, Department, Program). Workaround:- Map D365 “Department” dimension to Encore Health OS
department_id - Map D365 “Program” dimension to Encore Health OS
program_id - Map D365 “Grant” dimension to Encore Health OS
fund_id(create fund per grant) - Additional dimensions (Project, Location, etc.) stored in
custom_fieldsJSONB column
12.3 D365 BC Fixed Assets
Issue: Encore Health OS FA v1.0 does not include fixed asset module (depreciation, asset tracking). Workaround:- Migrate fixed asset GL account balances only (not detail records)
- Continue using D365 BC fixed asset module for depreciation
- Post monthly depreciation entries from D365 BC to Encore Health OS via journal entry
- Plan for fixed asset module in Encore Health OS FA v1.2 (Q3 2026)
13. Success Criteria
Migration is successful when:- All account balances reconciled to penny-level accuracy
- All open payables and receivables migrated and reconciled
- First month-end close completed successfully in Encore Health OS
- Financial statements match prior month D365 BC statements
- All users trained and comfortable with Encore Health OS FA
- No critical or high-severity issues outstanding
- CFO sign-off obtained
14. Contacts & Resources
Migration Project Manager:- Name: [TBD]
- Email: [TBD]
- Phone: [TBD]
- Name: [TBD]
- Credentials: D365 BC Functional Consultant
- Name: [TBD]
- Credentials: Encore Health OS Certified Developer
- Level 1: Implementation team
- Level 2: Encore Health OS Product Manager
- Level 3: Encore Health OS CTO
Document Status: OUTLINE - To be completed before migration begins
Next Review: Before Phase 1 kickoff meeting