Migrate from Everwin to Infor CloudSuite Corporate

Everwin Customer records map to Infor CloudSuite Business Partner records with a PartyType of Customer. We preserve the Everwin customer code as a custom reference field, the primary contact name, billing address, and payment terms. Business Partner is created before any related transaction records so that parent references are satisfied at insert time. In multi-site Everwin installations, the customer branch structure maps to separate Business Partner sites under a single party.

Everwin Vendor records map to Infor CloudSuite Business Partner records with a PartyType of Vendor. Payment terms, bank details, and the primary contact transfer to the Vendor Business Partner. We flag any Everwin Vendor that appears in open PO records as a prerequisite to PO migration so that the vendor record exists before the transaction references it.

Everwin Item records map to Infor CloudSuite Item records. SKU, item description, unit of measure, standard cost, and any custom attributes transfer. Custom item attributes that have no direct Infor equivalent are stored as extended data fields or mapped to user-defined fields in the Infor Item Master. We validate that each Item has a valid Unit of Measure code before insert.

The Everwin Chart of Accounts requires a full account code mapping to Infor CloudSuite GL Account codes. We export the complete Everwin account structure including account type, posting level, and any cost-center extensions, then present a reconciliation matrix to the customer before loading. The customer approves the mapping before GL Account import begins. Account codes that have no Infor equivalent are flagged for manual decision.

Everwin Tax Codes are tied to jurisdiction and must be mapped to Infor CloudSuite Tax Codes or tax configuration entries. We export the full Everwin tax code set and build a mapping table referencing the destination's tax codes by country and tax type (VAT, GST, sales tax). Some Everwin tax codes may be jurisdiction-specific and require manual entry in Infor Tax Configuration if no equivalent exists.

Everwin User records with roles and permissions map to Infor CloudSuite Employee or User records. We resolve by email address match. Any Everwin User without a matching Infor User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission profiles map to Infor Security Groups or responsibility assignments.

Everwin Project records with custom field extensions and status workflows map to Infor CloudSuite Project records. Status values require a value-mapping table because Everwin edition-specific workflow states differ between installations. We export the full Project record and its custom fields, then apply the per-customer value map before insert. Projects that reference non-existent Customers or Items are flagged and held for resolution.

Open Accounts Receivable and Accounts Payable transactions in Everwin's ERP module migrate as live Infor CloudSuite AR and AP records. The open balance, due date, invoice date, and counterparty reference transfer. We migrate open items only at cutover to avoid duplicating transactions already closed in Everwin during the migration window. A delta migration runs after cutover to capture any transactions entered between the final export and go-live.

Fully paid historical transactions from Everwin's ERP module migrate as Infor CloudSuite read-only journal entries. We load one to two years of history based on the customer's scope decision; older history is archived per the agreed retention scope. Historical entries are posted to the mapped GL Account codes and carry the original Everwin transaction date and amount. We flag any historical entries that reference unmapped account codes for the customer to resolve before loading.

Everwin user-defined custom objects are unique per installation. We introspect the source schema during scoping and build a per-customer field map for each custom object before migration. Destination Infor custom objects require pre-creation of the schema including all fields, data types, and lookup relationships. We do not attempt to migrate custom objects without a complete schema inspection because the field structure cannot be inferred from API responses alone.

Everwin document attachments are binary blobs linked to parent entities (Customer, Vendor, Project, Transaction). We export them with their parent reference and filename. In multi-tenant Infor CloudSuite, documents are stored in Infor Document Management or routed to an ION-connected external storage endpoint. We deliver the document package with parent references intact; the customer's Infor admin configures the document storage location during post-migration setup.