Migrate from Edicom to Odoo ERP

Edicom message flows (ORDERS, INVOIC, DESADV, PRICAT) map to Odoo purchase and sales document types. We extract the active flow configurations from Edicom during scoping, classify each by direction (inbound/outbound) and document type, and map them to Odoo's purchase.order, sale.order, and account.move models. Flows inactive for over 12 months are flagged as deprecated and excluded from migration scope unless the customer requests otherwise.

Edicom trading partner profiles (connection settings, supported document types, certification status, contact information) map to Odoo res.partner records. We preserve the partner EDI identifier (GLN, DUNS, AS2 ID) in a custom field on res.partner, and we maintain a lookup table linking each Edicom partner profile ID to the corresponding Odoo partner ID so that re-connection during cutover references the correct records. Inbound partners (those sending to you) map to res.partner with supplier=True; outbound partners (those receiving from you) map with customer=True or both depending on relationship direction.

Edicom translation maps contain source-to-destination field mappings and transformation rules between partner EDI formats and ERP data. These maps are platform-specific and cannot be directly imported into Odoo. We export map definitions as structured JSON metadata, document the field-level mapping logic, and deliver a written specification for the customer's Odoo developer or EDI middleware configuration team to implement. This is a handoff artifact, not a direct migration.

Edicom connects to ERP systems via middleware, intermediate tables, or direct API/WebService calls. The specific integration layer must be re-established in Odoo. We document the current integration architecture, identify every middleware endpoint and data flow, and deliver a specification for Odoo's XML-RPC or JSON-RPC integration rebuild. If the customer's ERP is Odoo itself (Edicom is connected to a separate ERP), the migration scope includes reconnecting those feeds directly within the Odoo instance.

Edicom captures the EDI standard (X12, EDIFACT, VDA, ODETTE) and version variant for each active connection. We export this as a configuration table and map it to Odoo's EDI module settings or to the equivalent configuration in the customer's chosen EDI middleware. Standard and version compliance per partner is preserved so that document validation rules at the destination match what partners expect.

TLS certificates, AS2/AS4 identifiers, and signing keys are provisioned under Edicom's account structure and cannot be directly transferred. We flag every certificate-bound connection during scoping and deliver a re-issuance schedule. The customer must coordinate with their certificate authority for new certificates and with trading partners for updated received-against certificates. This step is sequenced before the cutover window to avoid connectivity gaps.

Edicom EDICOMLta archive records migrate as Odoo account.move records for invoices and payments, purchase.order and sale.order records for historical orders, and stock.move records for shipments. We preserve the original Edicom document timestamp, message ID, and digital signature hash in custom fields on each migrated record. The customer retains Edicom archive access for the legally required retention period post-migration; exported files are treated as standalone records without native signature-validity context.

Customer-specific intermediate data tables and equivalence lists referenced in Edicom map logic are exported as structured lookup tables. We import these into Odoo as custom ir.model.data records or as dedicated custom models depending on their structure. We document the update frequency and trigger for each table so the Odoo team can maintain them as part of ongoing operations. This data is often undocumented and maintained by a single developer; discovery happens during the mapping phase and we flag any table with no identified owner.

Edicom transaction logs (timestamp, status, content hash per processed document) migrate to Odoo mail.message records linked to the parent document (account.move, purchase.order, sale.order). We preserve the original log timestamp and status code in mail.message body or custom fields. Logs are re-indexed in Odoo for query and filtering. The customer specifies the retention period during scoping; logs beyond that period are exported as flat files and not imported into Odoo.

Edicom's Managed Services provide 24x7 monitoring and administration for EDI operations. Migration requires a handoff plan so that Edicom's support team stops monitoring transferred connections and the new platform takes over. We deliver a monitoring requirements document specifying which Odoo connections require active monitoring, which Odoo.sh or third-party monitoring tools to configure, and the escalation contacts for each trading partner connection type.