ERP migration
Field-level mapping, validation, and rollback between daftra and Microsoft Dynamics 365 Business Central. We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Business Central.
daftra
Source
Microsoft Dynamics 365 Business Central
Destination
Compatibility
10 of 12
objects map 1:1 between daftra and Microsoft Dynamics 365 Business Central.
Complexity
BStandard
Timeline
6-8 weeks
Overview
Moving from Daftra to Microsoft Dynamics 365 is an ERP-to-ERP migration that requires resolving Daftra's undocumented API constraint during extraction, sequencing the Chart of Accounts before any transactional record, and normalizing Arabic-first locale data (dates, currencies, text encoding) to standards compatible with Dynamics 365. Daftra's multi-module schema maps across Finance, Supply Chain, and Human Resources app boundaries in Dynamics 365, which means the mapping must account for Business Central's single-database model versus Finance and Operations' separate data pods. We extract via vendor-coordinated API access where available and UI exports where not, build the account tree from Daftra's flat chart export using recursive parent-code resolution, and load the hierarchy into Dynamics 365 before any invoices, expenses, or employee records are inserted. Workflows, automations, and Daftra's Cheque Cycle tracking do not migrate as code; we deliver a written inventory of these for the customer's admin to rebuild in Dynamics 365.
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.
Source platform
daftra platform overview
Scorecard, SWOT, gotchas, and pricing for daftra.
Destination platform
Microsoft Dynamics 365 Business Central platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Business Central.
Data migration guide
The complete Dynamics 365 Business Central migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Dynamics 365 Business Central migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Business Central.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a daftra object lands in Microsoft Dynamics 365 Business Central, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
daftra
Clients
Microsoft Dynamics 365 Business Central
Customer
1:1Daftra Client records map to Dynamics 365 Customer (using the CustomerType field to set Account as the party type). Client follow-up history migrates as Notes or Activities linked to the Customer record. Membership points, insurance references, and sales commission balances migrate as custom fields on the Customer entity. The Customer Number is set from Daftra's client code; the Name field maps from the primary contact name in Daftra.
daftra
Products & Services
Microsoft Dynamics 365 Business Central
Item (Product and Service types)
1:1Daftra Products and Services export as Items in Dynamics 365 with the Item Type field distinguishing Inventory Item, Service Item, and Charge Type. SKU maps to Item Number; unit of measure comes from Daftra's product unit configuration. Stock levels migrate to Inventory Posting Group if the destination is Business Central with inventory enabled. Supplier links on Daftra products map to Vendor records in Dynamics 365.
daftra
Chart of Accounts
Microsoft Dynamics 365 Business Central
G/L Account (Chart of Accounts structure)
1:1Daftra's Chart of Accounts loads first, before any transactional records, to satisfy Dynamics 365's account-referenced posting requirement. We reconstruct the parent-child hierarchy from Daftra's flat account export using account code prefixes (e.g., accounts starting with 1xxx are assets, 2xxx liabilities). The Dynamics 365 account structure and account categories are assigned based on the account type. Sub-account relationships are resolved before import so that consolidated posting groups are valid.
daftra
Cost Centers
Microsoft Dynamics 365 Business Central
Dimensions (Department and Project)
lossyDaftra Cost Centers map to Dynamics 365 Dimensions as either Department or Project dimension values. We configure the global Dimension Set ID framework in Business Central so that Cost Center values can be applied to G/L entries, journal lines, and posted transactions. The mapping preserves the Cost Center attribution on Expenses and Invoices.
daftra
Invoices
Microsoft Dynamics 365 Business Central
Sales Invoice / Cust. Ledger Entry
1:1Daftra Sales Invoices map to Sales Invoices in Business Central or to Cust. Ledger Entries if posting occurred in Daftra. Line items reference Items and Account numbers resolved via the Chart of Accounts load. Tax amounts migrate to Tax Detail records using the VAT/Tax Group configuration. Installment schedules from Daftra are reconstructed as Payment Terms or as separate Reminder Entry records. Invoice balance and payment status are preserved in the Customer Ledger Entry open/closed flag.
daftra
Expenses
Microsoft Dynamics 365 Business Central
G/L Entry (Vendor Ledger Entry for AP)
1:1Daftra Expenses migrate to G/L Journal Entries with the G/L Account mapped from the Daftra expense category and the Department Cost Center mapped to the assigned Dimension. Recurring expense patterns are flagged with a Recurring Jnl. Batch designation for Dynamics 365 to regenerate. Vendor-related expenses map to Vendor Ledger Entries as Accounts Payable.
daftra
Employees
Microsoft Dynamics 365 Business Central
Employee (HCM Core or HR module)
1:1Daftra Employee records map to the Employee table in Dynamics 365 Human Resources or HCM Core. Compensation history (salary, bonuses, commissions tracked as time-series in Daftra) migrates as Employment History records with effective dates. Organizational structure assignments map to the Position and Department hierarchy in Dynamics 365. Attendance records migrate as Time Registration entries if the destination includes the Human Resources app.
daftra
Assets
Microsoft Dynamics 365 Business Central
Fixed Asset
1:1Daftra Fixed Assets map to the Fixed Asset register in Dynamics 365. Depreciation schedules are extracted from the Assets module and loaded as Depreciation Books attached to the Fixed Asset record. Custom fields added per-asset in Daftra are migrated as Fixed Asset custom fields in Dynamics 365. Asset postings (acquisition, depreciation, disposal) are loaded into the FA Ledger Entries table.
daftra
Work Orders
Microsoft Dynamics 365 Business Central
Job (Service Management or Project Operations)
1:1Daftra Work Orders map to Jobs in Dynamics 365 Project Service Automation or Service Management apps. The Work Order links to Client and Employee are preserved as Customer and Worker lookups on the Job card. Workflow stage history migrates as Job Task lines with milestone tracking. Attached files and notes migrate as Document Attachments on the Job record.
daftra
Bookings / Reservations
Microsoft Dynamics 365 Business Central
Service Order or Resource Attendance
1:1Daftra Reservation Files (PNR-style booking records) map to Service Orders or Resource Service Order lines in Dynamics 365 Service Management. Status tracking migrates to Service Order status fields. Appointment scheduling migrates as Resource Allocations with calendar-based time entries. Activity log on the reservation file migrates as Service Journal entries or Notes.
daftra
Cheque Cycle
Microsoft Dynamics 365 Business Central
Bank Account Ledger Entries / Check Ledger
1:1Daftra's Cheque Cycle (issue, deposit, return stages) maps to Bank Account Ledger Entries in Dynamics 365 with cheque number tracking enabled on the Bank Account. Each stage of the Daftra cheque cycle (issued, deposited, cleared, returned) maps to a separate Bank Account Ledger Entry with the relevant date and amount. The link to the originating Invoice is preserved via the Document No. field on the bank entry.
daftra
Custom Fields
Microsoft Dynamics 365 Business Central
Custom Fields (per entity)
lossyDaftra custom fields on Invoices, Assets, and Workflows are enumerated per object during discovery (Daftra has no global field registry). Each custom field is read for field type, required flag, and options list, then recreated as a custom field on the corresponding Dynamics 365 entity. Picklist-style custom fields in Daftra map to Option Sets in Dynamics 365; text fields map to Text fields with appropriate length. The custom field values are loaded after the entity schema is deployed.
| daftra | Microsoft Dynamics 365 Business Central | Compatibility | |
|---|---|---|---|
| Clients | Customer1:1 | Fully supported | |
| Products & Services | Item (Product and Service types)1:1 | Fully supported | |
| Chart of Accounts | G/L Account (Chart of Accounts structure)1:1 | Fully supported | |
| Cost Centers | Dimensions (Department and Project)lossy | Mapping required | |
| Invoices | Sales Invoice / Cust. Ledger Entry1:1 | Mapping required | |
| Expenses | G/L Entry (Vendor Ledger Entry for AP)1:1 | Fully supported | |
| Employees | Employee (HCM Core or HR module)1:1 | Mapping required | |
| Assets | Fixed Asset1:1 | Mapping required | |
| Work Orders | Job (Service Management or Project Operations)1:1 | Fully supported | |
| Bookings / Reservations | Service Order or Resource Attendance1:1 | Fully supported | |
| Cheque Cycle | Bank Account Ledger Entries / Check Ledger1:1 | Mapping required | |
| Custom Fields | Custom Fields (per entity)lossy | Mapping required |
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.
daftra gotchas
API is not publicly documented
Custom fields are object-scoped and must be enumerated per object
Chart of Accounts export does not flatten sub-account hierarchy
Arabic character encoding requires normalization
Microsoft Dynamics 365 Business Central gotchas
Named-user licensing has no concurrent-use relief
API rate limits throttle large-volume migrations
Historical posted transactions require selective migration scoping
NAV-to-Business Central cloud migration requires partner coordination
Custom fields and AL extensions require separate migration handling
Pair-specific challenges
Migration approach
Discovery and API access confirmation
We audit Daftra across all active modules (CRM, HRM, Accounting, Inventory, Operations) to enumerate record counts, custom field definitions, active workflows, and the chart of accounts structure. We simultaneously confirm API access with Daftra's technical team or define the UI export protocol if API access is unavailable. This phase produces a written migration scope, record-count estimate, and a risk flag if API access coordination is still outstanding. We hold a timeline contingency of two to four weeks if API access requires vendor engagement.
Destination app selection and schema deployment
We confirm the target Dynamics 365 application (Business Central for SMB-mid market; Finance and Operations for enterprise with multi-entity, multi-country, or advanced supply chain needs). We deploy the base schema to a Dynamics 365 Sandbox: the Chart of Accounts structure with G/L Account categories, Dimension configurations for Cost Centers, Item types for the product catalog, and the Employee table. Custom fields are pre-created on each entity before data migration begins. Schema is deployed via the Dynamics 365 administration center or LCS for Finance and Operations.
Chart of Accounts tree reconstruction and load
We process Daftra's flat account export to reconstruct the parent-child hierarchy using account code pattern analysis. Each account is assigned a G/L Account category (Asset, Liability, Equity, Revenue, Expense), a Posting Group, and a direct parent reference. The complete account tree is validated against Daftra's trial balance total before load. We load accounts in account code sequence to respect posting order, then validate the total debit and credit balances against Daftra's balance sheet to confirm the tree is intact before any transactional data phase begins.
Master data migration in dependency order
We load master data in strict dependency order: G/L Accounts (complete, validated), Dimensions (Cost Centers), Customers, Vendors, Items (Products and Services), Employees, and Fixed Assets. Each phase emits a row-count reconciliation report against the Daftra source. Custom fields on each entity are loaded after the base record is created. Arabic character normalization and date conversion run as a pre-transform step before each phase.
Transactional data migration and cheque cycle reconstruction
We load open and historical invoices, expenses, and journal entries against the validated account and customer master. Installment schedules are reconstructed as Payment Terms on customer records or as separate Reminder Entry lines. The Daftra Cheque Cycle (issue, deposit, return) is reconstructed as Bank Account Ledger Entries with cheque number tracking, linked to the originating invoice document. Work Orders and Bookings load as Jobs or Service Orders after the Customer and Employee masters are validated.
Sandbox reconciliation and production cutover
We run a full migration into a Dynamics 365 Sandbox and compare record counts, account balances, and open invoice totals against Daftra. The customer's finance lead spot-checks 25-50 records and signs off before production migration begins. We freeze Daftra writes during cutover, run a final delta migration for any records modified during the window, then hand off to the customer's admin for workflow and automation rebuild in Power Automate. We support a one-week hypercare window for reconciliation issues raised by the customer's team.
Platform deep dives
daftra
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Business Central
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between daftra and Microsoft Dynamics 365 Business Central.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across daftra and Microsoft Dynamics 365 Business Central.
Object compatibility
All 8 core objects map 1:1 between daftra and Microsoft Dynamics 365 Business Central.
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
daftra: Not publicly documented.
Data volume sensitivity
daftra 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 daftra to Microsoft Dynamics 365 Business Central migration scoping. Not seeing yours? Book a call.
Walk through your daftra to Microsoft Dynamics 365 Business Central migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave daftra
Other ways to arrive at Microsoft Dynamics 365 Business Central
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.