Migrate from Edicom to Microsoft Dynamics 365 Business Central

Edicom trading partner profiles contain connection settings, supported document types (ORDERS, INVOIC, DESADV), certification status, and contact information. We export profiles and map them to Dynamics 365 Vendor records (for inbound EDI from suppliers) or Customer records (for outbound EDI to buyers), with communication method and address data preserved in the standard address structure. Partner EDI identifier (GLN, DUNS) migrates to the vendor/customer Global Location Number field.

Each Edicom message flow (which EDI transaction types are active per trading partner) maps to a Dynamics 365 Data Entity configured for the corresponding inbound or outbound integration template. We export flow configurations as structured metadata and document which Data Entities (such as Vendors, Customers, Purchase Orders, Sales Orders, or Project Transactions) handle each document type at the destination.

Edicom translation maps (source/destination field mappings and transformation rules between partner EDI formats and ERP data structures) are exported as structured map definitions. At Dynamics 365, equivalent transformation logic is implemented via the Data Management Framework field mapping, Azure Logic Apps transformations, or custom data entities. We flag maps that rely on undocumented intermediate data tables as high-risk and flag maps for inactive trading partners for exclusion.

Many Edicom implementations use customer-specific intermediate data tables and equivalence lists referenced in map logic but not exposed as first-class platform objects. These are often maintained by a single developer and undocumented. We discover all referenced tables during scoping, export their contents as structured data, and replicate them as Dynamics 365 lookup tables (custom fields with option sets) or Azure SQL lookup databases linked via Logic Apps.

Edicom connects to the customer's ERP via middleware, intermediate data tables, or direct API calls. The specific integration layer must be re-established at Dynamics 365 using Azure Logic Apps, Power Automate, or the Dynamics 365 Data Management Framework. We document the current integration architecture during scoping and provide a connection architecture plan for the destination.

Edicom supports X12, EDIFACT, VDA, ODETTE, UBL, and TRADACOM standards with version variants per trading partner. We capture the standard and version for each active connection and map to the equivalent EDI configuration in Dynamics 365 Finance and Operations or the third-party EDI add-on the customer selects. Standard/version mismatches are flagged during mapping for partner-by-partner resolution.

AS2/AS4 certificates, TLS credentials, and signing keys are provisioned under Edicom's account structure and cannot be transferred directly. We flag every certificate-bound connection during scoping, create a certificate re-issuance schedule coordinated with the cutover window, and recommend Azure Key Vault for certificate storage at the destination. Each trading partner must be notified and may need to update their received-against certificate or AS2 identifier.

Long-term archive records store transaction evidence with timestamping and digital signatures. We export archive records as structured data with evidentiary metadata (timestamp, content hash, certificate chain) preserved. At Dynamics 365, records are stored in SharePoint Online document management or Dataverse with Microsoft Purview compliance retention labels applied. We advise retaining Edicom archive read access or re-validating signatures before treating exported files as standalone legal records.

Edicom transaction logs capture timestamp, status, and content hash for each processed document. We export historical logs for the retention period the customer specifies and re-index them in Dynamics 365 Dataverse audit logs or Azure Monitor for querying. Audit trail integrity is preserved by carrying forward the original document hash values as custom fields on the imported records.

Edicom operates as a Qualified Trust Service Provider in Europe, Mexico, and Colombia for electronic signatures, timestamping, and certified delivery. Microsoft Dynamics 365 does not include a built-in Trust Service Provider; organizations with regulatory requirements for qualified electronic signatures or certified delivery must re-engage a Microsoft-certified PDP or Trust Service Provider post-migration. We inventory active Trust Service configurations during scoping and include the provider handoff plan in the migration documentation.

Edicom Managed Services covers 24x7 monitoring and administration of EDI connections. Migration requires a handoff plan so that Edicom's support team stops monitoring transferred connections and the new Dynamics 365 or Azure Logic Apps integration takes over active monitoring. We configure Azure Monitor alerts and Dynamics 365 alert rules during cutover to maintain equivalent operational visibility.

Edicom document approval workflows (e-signature approval processes with steps, conditions, and assigned users) map to Dynamics 365 Power Automate flows or standard Dynamics 365 Workflow. We document the approval chain, condition logic, and user assignments from Edicom and deliver a written workflow design for the customer's admin to configure in Power Automate, noting that the approval UI and signature integration must be rebuilt using Dynamics 365 e-signature connectors or Power Automate approval actions.