Migrate from metasfresh to Microsoft Dynamics 365 Business Central

metasfresh C_BPartner stores both customers and vendors in a single table with a Partner Type flag (C_BPartner_Type). We split this into separate Dynamics 365 CustCustomerV3Entity (Customer) and VendVendorV2Entity (Vendor) records. Address records (C_BPartner_Location) map to DirPartyPostalAddressV2Entity and DirPartyPostalAddressV2Entity with address purpose roles. Contact points (C_BPartner_Contact) map to LogisticsPostalAddressContactMechanismV2Entity. The vendor vs customer classification is preserved in a custom field mf_partner_type__c for reconciliation.

metasfresh M_Product maps to Dynamics 365 EcoResReleasedProductV2Entity. Product type (Item vs Service vs Resource) maps to ProductType. Product categories (M_Product_Category) map to InventProductCategoryV2Entity and EcoResProductCategoryAssignmentEntity. The metasfresh UPC/EAN from M_Product value maps to EcoResProductIdentifierV2Entity with GTIN type. Stock control status (M_Product_Stock) maps to InventOnHandWarehouseAttributeEntity. We exclude any M_Product records flagged as discontinued if the customer has not activated the corresponding discontinued status in Dynamics 365.

metasfresh sales orders (C_Order header and C_OrderLine) map to SalesOrderHeaderV3Entity and SalesOrderLineV2Entity. The order date (DateOrdered), promised date (DatePromised), and document status map directly. SalesOrderLine includes product number, quantity, unit, and price from C_OrderLine. Header-level charges (C_OrderLine where M_Product_ID is null) map to SalesOrderHeaderChargeEntity. We require the Business Partner and Product records to exist before order lines load because Dynamics 365 enforces referential integrity on CustomerAccountNumber and ItemNumber.

metasfresh purchase orders (C_Order with IsSOTrx = N) map to PurchPurchaseOrderHeaderV2Entity and PurchPurchaseOrderLineV2Entity. The vendor account reference, order date, and expected delivery date migrate directly. Line-level delivery date (C_OrderLine DeliveryDate) maps to PurchPurchaseOrderLineV2Entity ExpectedDeliveryDate. Purchase order approval workflow status in metasfresh maps to WorkflowState in Dynamics 365 if the customer has the same approval workflow configured post-migration.

metasfresh AR invoices (C_Invoice and C_InvoiceLine) map to either CustFreeTextInvoiceV2Entity or CustInvoiceV3Entity depending on whether the customer uses free-text or posted sales invoices in Dynamics 365. Invoice lines map to CustInvoiceLineV2Entity with LineAmount, TaxCode, and SalesTaxGroup fields populated. The original invoice number from metasfresh C_Invoice DocumentNo maps to ExternalInvoiceNumber for audit trail. We require the Customer account to exist before AR invoice migration because CustAccount is a required lookup.

metasfresh AP invoices map to VendVendorInvoiceV3Entity (header) and VendVendorInvoiceLineV2Entity (line). The vendor account number, invoice number, invoice date, and due date migrate directly. Tax information from C_Tax (tax code and rate) maps to TaxGroupId and TaxCodeId on the invoice line. We verify that the vendor account is provisioned before AP invoice load to satisfy the AccountNum required field.

metasfresh pricing is organized into Pricing Schemas containing versioned price lists with effective dates (ValidFrom, ValidTo). We map each M_PricingSchema to a Dynamics 365 PriceDiscTable (price list) and PriceDiscTableVersion (version). The version effective date maps to PriceDiscTableVersion.FromDate. Individual price lines from M_ProductPrice map to PriceDiscAdmTrans or ecobResProductPrice entity depending on whether the destination is Business Central or Finance & Operations. We flag any prices with no ValidTo date as open-ended and document this for the customer's pricing administrator.

metasfresh bill of materials records (pp_product_bom header and pp_product_bomline components) map to BOMTable and BOMLine in Dynamics 365 SCM. We inspect pp_product_bom for Active status and include only lines where the MRP module (IsActive flag on pp_product_bom) is enabled. Component quantities and scrap percentages from pp_product_bomline map to BOMLine.Qty and BOMLine.BOMLineRouteRelation_Old.ScrapPercent. The finished product reference from pp_product_bom.M_Product_ID maps to BOMTable.ItemId. We flag any BOM with more than 50 components for customer review before migration because large BOMs may require Phantom BOM or versioned BOM strategy in Dynamics 365.

metasfresh projects (C_Project and C_ProjectLine) map to ProjProjectV2Entity and ProjForecastLineEntity. Project type (WBS, Time and Material, Fixed Price) from C_Project.ProjectType maps to ProjProjectV2Entity.ProjTypeId. Project lines (phases, tasks, and cost categories) from C_ProjectLine map to ProjProjectLineV2Entity with ProjLineType区分. Hourly cost rates from C_ProjectLine map to ProjCostPriceTableEntity for Time and Material billing. We map the owning Business Partner from C_Project.C_BPartner_ID to ProjProjectV2Entity.CustAccount for customer-linked projects.

metasfresh bank accounts (C_BP_BankAccount linked to C_BPartner) map to BankAccountTable in Dynamics 365. IBAN, SWIFT/BIC, and bank name from the source record map to BankAccountTable.IBAN, BankAccountTable.SWIFTNo, and BankAccountTable.BankName respectively. The bank account is scoped to the legal entity via BankAccountTable.LegalEntityId. Payment identification methods in metasfresh (e.g., SEPA, ACH) map to BankAccountTable.NumberSequence for payment format configuration.

metasfresh payment terms (C_PaymentTerm) map to PaymTermTable in Dynamics 365. Fields including NetDays (net due days), GraceDays (grace period), and discount percentages (DiscountDays, DiscountPercent) map directly to PaymTermTable.NetDays, PaymTermTable.GraceDays, PaymTermTable.DiscountPercentage, and PaymTermTable.DiscountValidityDays. We include all C_PaymentTerm records regardless of usage count and flag any terms with atypical day calculations (e.g., month-end + fixed days) for the customer's AP team to verify post-migration.

metasfresh tax configurations (C_Tax with C_TaxCategory assignment) map to TaxCode (TaxTable) and TaxGroup (TaxGroupTable) in Dynamics 365. The tax rate percentage and description from C_Tax map to TaxCode.SalesTaxRate and TaxCode.TaxName. Geographic applicability (C_TaxCountryRegion) maps to TaxCode.CountryRegionId and TaxCode.StateId for multi-jurisdiction tax setups. Effective date ranges from C_Tax.ValidFrom and ValidTo map to TaxCode.FromDate and TaxCode.ToDate. We exclude any tax records marked as inactive in metasfresh.

metasfresh custom fields discovered via AD_Column metadata query (ColumnSQL, IsCustomColumn = Y) map to custom attributes on the corresponding Dynamics 365 entity. We inspect AD_Column during discovery to identify all per-table custom fields and include them as additional columns in the PostgreSQL export query. Field data type from AD_Column.AD_Reference_ID maps to the nearest Dynamics 365 field type (string to Text, integer to Int, decimal to Real). Custom field values are appended as additional columns in the import CSV and loaded into the destination custom field after the standard fields are validated.

metasfresh stores archived invoice PDFs and file attachments as byte arrays in the database (AD_Attachment) or as file system references whose paths are not consistently tracked in metadata tables. There is no supported export path for these objects. We flag this explicitly during scoping and exclude attachments from the migration deliverable. The customer receives a written instruction document for manually retrieving attachments via direct PostgreSQL blob extraction or filesystem access if they require them in Dynamics 365 SharePoint or Dataverse document management post-migration.