Migrate from Exact Globe to Microsoft Dynamics 365 Business Central

Exact Globe Accounts map to both Microsoft Dynamics 365 Customer records (for debtors/receivables) and Vendor records (for creditors/payables). We extract the account_type field to determine the split. Customer and Vendor numbers are generated from the Exact Globe account code. Address, payment terms, and tax registration fields migrate directly. Custom fields on the Exact Globe Account table map to custom fields on Customer and Vendor in Dynamics 365.

Exact Globe journal entries and their line items are stored in separate but related tables. We extract entry-level metadata (date, journal code, description) and line-level data (G/L account, debit amount, credit amount, dimension). Exact Globe dimensions (cost center, project, department) map to Dynamics 365 Dimensions (Global Dimensions and shortcut dimensions). Locked or reconciled periods in Exact Globe require explicit date-range scoping during export to avoid posting to locked fiscal periods in Dynamics 365.

Sales and purchase invoices in Exact Globe split into header and line tables. We preserve the relationship via invoice number keys. Tax codes, payment terms, and invoice status (open, paid, cancelled) migrate to Dynamics 365. Posted invoices in Exact Globe create posted Sales Invoice records or posted Purchase Invoice records in Dynamics 365. Invoice attachments are flagged as a manual handoff because Exact Globe stores attachments in database blobs not reliably accessible via API.

Exact Globe Items (products, services, and variants) map to Dynamics 365 Item records. We extract item code, description, unit of measure, cost price, and sales price. BOM associations are preserved for migration to the Dynamics 365 BOM module. Stockkeeping units and variant codes map to Dynamics 365 Item variants. Item tracking (lot numbers, serial numbers) migrates to Dynamics 365 Item Tracking.

Exact Globe BOMs define multi-level product structures with component items, quantities, and routing steps. Exporting BOMs requires recursive traversal of sub-assemblies, which we handle in staged extraction passes. Multi-level BOMs in Exact Globe map to Dynamics 365 Production BOMs with parent-child component lines. Routing steps with work centers map to Dynamics 365 Routes with work centers and capacity. We flag any BOM that exceeds the Dynamics 365 nesting depth limit for admin review before migration.

Exact Globe orders split into header and line rows. Order status (open, processed, invoiced) and back-order relationships are preserved through ID key mapping. Partial shipment handling in Exact Globe maps to Dynamics 365's drop-ship and special-order capabilities. Open orders are migrated as draft orders in Dynamics 365; closed orders are migrated as historical records with their original status preserved for audit.

Exact Globe Quotations are header-level documents with line items. Conversion status (expired, converted to order) is stored as a flag and maps to Dynamics 365's Quote Status field. Expired quotes are migrated with expired status for historical reference. Active quotes are migrated as open Sales Quotes in Dynamics 365. Quote expiration dates migrate as-is.

Project accounting is embedded throughout Exact Globe. We extract project headers, cost categories, billing methods, and budget data. Project-related time entries are a separate object and migrate to Dynamics 365 Project Timesheet lines. Billing methods (time and material, fixed price) map to Dynamics 365 Job posting groups. Work-in-progress calculations in Exact Globe migrate to Dynamics 365 Job calculation groups.

HR data in Exact Globe covers employee records, compensation, and organizational structure. Effective-dated changes are stored transactionally, which requires careful sequencing during export to preserve historical accuracy. Employee addresses, employment status, and compensation bands migrate to Dynamics 365 Employee records. Organizational hierarchy maps to the Dynamics 365 dimensions or the Human Resources organizational unit structure. Payroll data migrates as compensation history; active payroll processing requires a separate payroll configuration in Dynamics 365.

Contact persons are linked to Accounts but have independent records in Exact Globe. We extract name, role, email, phone, and address fields. In Dynamics 365, Contacts are linked to Customer records (from the Exact Globe Account mapping). Contact person ownership and lifecycle-stage assignments map to custom fields in Dynamics 365 because the native contact lifecycle model differs from Exact Globe's structure.

The Chart of Accounts and all posted journal entries are available for export. We handle account codes, descriptions, account groups, and posting history. Account types (balance sheet, income statement, expense) map to Dynamics 365 G/L Account types. Account schedules from Exact Globe do not migrate; we deliver a written map of every account schedule for rebuilding in Dynamics 365's Account Schedule or financial reporting module.

Fixed asset records include acquisition cost, depreciation method, book value, and asset class. Depreciation schedules must be recalculated in Dynamics 365 if the fiscal year calendar differs between Exact Globe and Dynamics 365, requiring a date-range check during scoping. Asset maintenance schedules migrate to Dynamics 365 Fixed Asset maintenance if the FA module is licensed. Depreciation books map to Dynamics 365 Depreciation Books with the same method and percentage assignments.

Exact Globe allows custom fields (text, long, double, date, bit) on 14 standard tables including Financial entries, Accounts, Invoices, Items, Orders, Projects, HR, and Contact persons. We catalog every custom field during discovery, confirm field types and lengths, then pre-create equivalent custom fields in Dynamics 365 before extraction begins. Custom field mapping is locked after scoping confirmation because Exact Globe does not allow editing of field names or types after creation.

Exact Globe stores file attachments within the database as binary blobs or on local/network file-system paths referenced by the application. Neither storage pattern is reliably retrievable via the public API. We flag all attachment-containing records during extraction and provide a manual file-export checklist to the customer as a post-migration step. Dynamics 365 uses SharePoint Online or Azure Blob Storage for document management, so the customer uploads exported files to the relevant SharePoint document library or Blob container post-migration.