Migrate from Everwin to Microsoft Dynamics 365 Business Central

Everwin Customer records map to Dynamics 365 Customer (which is a polymorphic Party type serving both Account and Contact roles) in Finance and Supply Chain, or to Account in Business Central. The customer's primary contact, billing address, and payment terms migrate as related Dynamics address records. We resolve the primary key from Everwin's Customer ID and store it in a custom field everwin_customer_id__c for audit and reconciliation.

Individual Contact records within Everwin's Customer entity map to Dynamics 365 Contact. Where Everwin stores a company-level Customer with multiple contact persons, we split these into separate Contact records linked to the corresponding Account. Email, phone, and role fields migrate directly; role/position fields map to Dynamics JobTitle or a custom contact role field.

Everwin Project records map to Microsoft Dynamics 365 Project Service Automation (PSA) Project or to a custom Project entity in Finance and Operations depending on the destination app licensed. Everwin custom field extensions on Project require schema profiling before migration, and we build a per-customer value-mapping table for project status workflows that differ between Everwin editions. Project task hierarchies migrate as WBS tasks in the destination.

Everwin document attachments are binary blobs linked to parent entities. We export documents with their parent reference and filename, preserving the association to Customer, Project, or Transaction. The destination location is either a SharePoint document library (SharePoint integration enabled) or Dataverse notes attachments, depending on the customer's Dynamics 365 configuration. Binary format and storage location vary by Everwin installation and must be confirmed during scoping.

Everwin User accounts with roles and permissions export via the API. We map them to Dynamics 365 User records, preserving email address (used as the username in Microsoft 365-integrated deployments), full name, and role assignments. Role mapping is configuration-dependent: Everwin's permission model does not have a direct Dynamics equivalent, so the customer's admin reviews the role mapping during scoping.

Open accounts payable and accounts receivable in Everwin migrate as open Vendor Ledger Entries and Customer Ledger Entries in Dynamics 365 Finance or Business Central. Invoice amounts, due dates, currency, and payment terms map directly. Outstanding balance and aging info migrates as open items linked to the corresponding Vendor or Customer record.

Fully paid historical transactions migrate as read-only General Ledger journal lines. We preserve account code, debit/credit amounts, transaction date, and description. These records are posted to a closed period in Dynamics to maintain the audit trail without allowing further modification, which aligns with standard ERP close procedures.

Everwin's chart of accounts requires a full account code reconciliation matrix before loading into Dynamics 365. We export the complete account structure from Everwin, present the customer with a reconciliation spreadsheet mapping each Everwin account code to the nearest Dynamics G/L Account, and load into the destination only after sign-off. Account dimensions (Cost Center, Department, Business Unit) also require mapping if Everwin uses dimension tagging.

Tax codes are jurisdiction-specific and tied to Everwin's regional configuration. We export the existing tax code set and build a mapping table referencing the destination's supported tax codes (Sales Tax, VAT, GST) in the customer's Dynamics 365 company. The customer validates the tax code mapping during scoping because mismapped tax codes affect invoice posting and compliance reporting.

Everwin Vendor records map directly to Dynamics 365 Vendor. Payment terms, bank details, and contact information migrate as Vendor address and contact records. Vendor hold status migrates as a Vendor Block in Dynamics Finance or as a Vendor credit limit flag in Business Central.

Everwin Item records include SKU, description, unit cost, and custom attributes. SKU maps to Dynamics Item Number. Pricing migrates to Item Unit Price and, where a Price List exists in Dynamics, to the appropriate Sales Price or Purchase Price record. Custom attributes require schema profiling to determine whether they map to Dynamics custom fields or to Item attributes tracked via the Item Attribute functionality in Business Central.

Everwin custom objects are user-defined and unique per installation. We introspect the schema at scoping, pre-create equivalent custom tables in the Dynamics 365 Dataverse or Business Central (depending on destination app), and build a per-customer field map before migration. Lookup relationships to standard objects (Customer, Project, Vendor) require parent-record resolution at migration time. Custom object migration is scoped as a separate phase after standard object validation is complete.