Migrate from Jeeves ERP to Microsoft Dynamics 365 Business Central

Jeeves stores a hierarchical chart of accounts covering balance sheet and P&L account types. We map account codes, account names, and account types directly into the Dynamics 365 G/L Account table. Account categories (Asset, Liability, Equity, Revenue, Expense) map to the Dynamics 365 G/L Account Category field. The full dimensional structure migrates into the destination Chart of Accounts, and we preserve the original Jeeves account codes as a reference field for audit traceability.

Jeeves Customer records include contact details, billing and shipping addresses, credit limits, and payment terms. We map these to the Dynamics 365 Customer card (name, address, contact information, payment terms, customer posting group). For Finance & Operations destinations with multiple legal entities, we preserve the Jeeves entity assignment and map to the corresponding Customer account within each legal entity. Multi-currency settings on the customer migrate to the Currency field.

Jeeves Vendor master records mirror the customer structure with supplier-specific fields including payment terms, bank details, and multi-currency settings. We map Vendors to the Dynamics 365 Vendor card with the same field-level precision. For Finance & Operations, vendor records are scoped to the operating company unless the customer uses cross-company procurement, which we configure during entity mapping.

Jeeves Items cover both products and materials with BOM structures, routing assignments, cost layers, and unit-of-measure settings. We migrate Items preserving the product type (Stockkeeping, Service, or Non-stock), costing method, and standard cost. For Finance & Operations destinations, Items migrate to the Released Product entity and we preserve the costing version reference. Custom fields on Jeeves Items map to extension fields on the destination Item card.

Outstanding payables and receivables in Jeeves are standard ledger documents with line-item detail, due dates, and amounts. We migrate open AP and AR as open ledger entries in the destination, preserving invoice numbers, voucher numbers, due dates, and remaining amounts. Closed documents migrate as historical entries to maintain the full ledger audit trail. Jeeves multi-currency invoice amounts migrate with the original currency and exchange rate preserved for reconciliation.

Jeeves journal entries carry date, description, debit/credit lines, and account assignments. We migrate journal entry header and line data preserving the journal entry numbering scheme, reversing entry flags, and posting dates. For Finance & Operations destinations with multiple legal entities, inter-company journal entries are mapped to the appropriate source and destination legal entity. Historical journal volume is scoped with the customer during planning to apply date-based filters and batch sizing.

Fixed assets in Jeeves include acquisition cost, depreciation schedule, asset category, and book value. We migrate the asset master with its acquisition date, cost, and depreciation method into the Dynamics 365 Fixed Asset card. Depreciation conventions and schedules migrate to the Fixed Asset Book, and depreciation methods are mapped to the nearest equivalent Dynamics 365 depreciation profile. Country-specific depreciation rules in the Expand edition are preserved as comments for the destination localization.

Manufacturing BOMs and routing definitions are core Jeeves objects in the Grow and Expand editions. We map BOM structures and work center assignments, preserving multi-level BOM hierarchies and alternate routing definitions. Multi-level BOMs require careful sequencing because child BOMs must exist before parent BOMs can reference them. We build a dependency graph from the Jeeves BOM data before initiating the migration, and we load parent and child BOMs in topological order. For Finance & Operations destinations, routings map to Route entities with work center references.

Jeeves Projects support time tracking, expense recording, and resource assignments. We map project records with associated tasks, milestones, and time entries into the destination's project management module. Project status, customer assignment, and billing method migrate as project type and work template settings. Time entries become project journal lines or time and material lines depending on the destination product edition.

Open orders in Jeeves with header and line-item detail, delivery schedules, and pricing migrate as Sales Order and Purchase Order records in Dynamics 365. We preserve quantities, line-item descriptions, unit prices, and delivery dates. Lines referencing items not yet migrated are held in a staging queue and processed after the Item master migration completes. Closed orders migrate as historical records.

Jeeves user records include role assignments, team memberships, and permissions. We migrate user accounts as Employee records (for Finance and HR data) and system User accounts in Dynamics 365. Role mappings are destination-specific: Jeeves role names map to Dynamics 365 security roles or user groups, and the customer's admin validates the final permission set against the destination's security model.

Jeeves supports document attachments on most business objects. We export attachments as binary files and re-associate them to the migrated parent record in Dynamics 365. In Business Central, attachments link via the Record Link table; in Finance & Operations, they link via the ElectronicDocument or Attachment framework. Large attachment volumes in the GB range require dedicated storage provisioning before migration begins.

Jeeves stores full transaction history at the ledger level. Volume of historical records can be large depending on the customer's tenure with Jeeves. We scope historical transactions with the customer during planning, applying date-based filters and chunking by fiscal year. Customers targeting Business Central SaaS should be aware of database size implications; we recommend archiving pre-3-year records into a reporting archive rather than migrating all history into the live database.

Jeeves process-based automation engine defines customer-specific workflows for approvals, alerts, and cross-module triggers that are tightly coupled to the instance's configuration. We do not migrate automation rules as executable logic. We document every automation rule we observe during scoping — including its trigger conditions, actions, and assigned roles — and deliver this as a specification document for the customer's Dynamics 365 implementation team to rebuild in Power Automate (Business Central) or X++ and Azure Logic Apps (Finance & Operations).