Migrate from Perfecto ERP to Microsoft Dynamics 365 Business Central

Perfecto ERP's multi-level hierarchical account structure maps to D365 F&O's Chart of Accounts with each account level mapped to a Financial Dimension set. We preserve the parent-child relationships from Perfecto and configure the account type (ProfitLoss, BalanceSheet, Expense) in D365 before import. Perfecto account codes longer than D365's character limit require truncation or prefix mapping; we flag this during the discovery phase.

Perfecto ERP General Ledger entries map to D365 F&O GeneralJournalLine entities. We preserve journal batch numbering from Perfecto's journal naming sequences and map debit and credit amounts to the D365 LedgerDimension field. Account offsets for tax and charges in Perfecto require explicit D365 Financial Dimension mapping to avoid posting to incorrect ledger accounts during import.

Perfecto ERP Customer records map directly to D365 F&O CustCustomerV2Entity. Address, contact, and payment term fields transfer 1:1 unless End-User Customization Studio added non-standard fields, which we flag before import. Customer posting profiles require mapping to D365's posting profile structure and must be configured in D365 before the first customer import batch runs.

Perfecto ERP Vendor records map to D365 F&O VendVendorV2Entity following the same structure as Customer mapping. Vendor-specific fields including tax registration numbers and payment hold flags map to corresponding D365 fields. We validate that vendor tax registration numbers conform to the D365 tax setup before loading.

Perfecto ERP Items (finished goods, raw materials, services) map to D365 F&O EcoResReleasedProductV2Entity. We map Perfecto item type, unit of measure, and cost price to D365 product type, unit conversion, and costing version. Inventory posting groups from Perfecto require mapping to D365 inventory model groups (FIFO, Standard, Moving Average) to ensure inventory valuation continuity.

BOM structures in Perfecto ERP create parent-component Item dependencies that must be migrated in correct order. We run a BOM dependency analysis before migration to build the import sequence: items with no BOM references load first, then BOM parents, then BOM components in dependency depth order. We validate BOM line quantities and route references post-load in D365. Silent data loss occurs if BOM components reference Item IDs that did not exist at import time; we prevent this through the sequencing approach.

Perfecto ERP Employee records map to D365 F&O HcmWorkerV2Entity with HR fields (job title, department, employment type) transferred directly. Role-based security assignments from Perfecto's Roles and Permissions matrix map to D365 Security Roles during the user provisioning phase. Workers without an associated D365 User account are imported as inactive and activated after the customer's admin provisions the User record.

Perfecto ERP file attachments are stored as file references linked to records. We export files to an Azure Blob Storage container or SharePoint document library, then create document location records in D365 F&O that link the file to the corresponding entity (Customer, Vendor, Employee, or Project). File attachment paths are not portable between systems; we perform the export and relinking as part of the migration.

Perfecto ERP purchase orders map to D365 F&O PurchPurchaseOrderV2Entity with header and line fields transferred. Approval workflow routing that exists in Perfecto ERP does not migrate; we document the approval chain as a written specification for the customer to rebuild in D365 Workflow Designer.

Perfecto ERP sales orders map to D365 F&O SalesSalesOrderV2Entity. Line items, pricing, and tax information transfer directly. Sales agreement references in Perfecto require mapping to D365's Sales Agreement construct if the customer uses blanket orders.

Approval Workflows and custom approval chains in Perfecto ERP are configuration data, not records. We extract the full workflow definition (trigger conditions, approver assignments, routing rules, escalation paths) as a written specification document. We do not migrate workflows as executable code because D365 Finance & Operations Workflow Designer uses a different schema. The customer's admin rebuilds approvals in D365 Workflow Designer or Power Automate using the specification we deliver.

Perfecto ERP's Roles and Permissions matrix maps conceptually to D365 F&O's Security Role-Duty-Privilege hierarchy. We extract the role-permission matrix from Perfecto and produce a written role mapping guide that identifies the closest D365 F&O Security Role for each Perfecto role, noting any permissions that do not have a direct D365 equivalent and require manual post-migration review.