Migrate from weclapp erp to Infor CloudSuite Corporate

weclapp Customer records map to Infor Business Partner with role=Customer. Address, tax ID, and payment terms transfer directly. Infor requires country-specific tax setup (MwSt/UST-IdNr for Germany) that must be entered in the destination forms before customer import; we flag this as a prerequisite step. The dedupe key is tax ID or email domain.

weclapp Company records (B2B accounts distinct from individual contacts) map to Infor Business Partner with role=Company. If weclapp is used for both customer companies and supplier companies, the role assignment is determined by the hasCustomerFlag or hasSupplierFlag on the source record. Companies without either flag are imported as Prospect role for admin review.

weclapp Items (products and services with SKU, description, unit price, and stock quantity) map to Infor Item master. Stock-on-hand figures transfer to Infor's inventory ledger; pricing tiers map to Price Lists. Infor requires warehouse and uom (unit of measure) setup before inventory quantities can be posted. Service items use the Service item type in Infor without stock tracking.

weclapp Sales Orders map to Infor Sales Order with Customer, Item, quantity, pricing, and status preserved. Order status from weclapp maps to Infor's order workflow states; the mapping is confirmed against the customer's active Infor sales process during scoping. Historical closed orders transfer as read-only records.

weclapp Purchase Orders map to Infor Purchase Order with Vendor, Item, quantity, and agreed price preserved. Vendor must be imported as a Business Partner with role=Supplier before Purchase Order import. Infor enforces approval workflows on PO types that weclapp does not; we flag any PO that requires approval routing in Infor but had no approval in weclapp.

weclapp Quotes (Sales Quotations with validity dates and pricing) map to Infor Sales Agreement or Quote depending on the Infor edition and configuration. Quoted items transfer as line items; we flag whether the destination uses time-limited agreements or static quotes during scoping. Expired quotes are not migrated unless the customer requests historical quoting records preserved.

weclapp Invoices map to Infor AR Invoice (for customer invoices) or AP Invoice (for vendor invoices). Paid and closed invoices transfer as historical read-only records; we flag any invoice that has been reconciled in weclapp to prevent inadvertent re-activation at the destination. Tax codes require manual recreation in Infor's tax configuration before invoice import because they do not export as standalone records.

weclapp Projects with nested Tasks and time entries map to Infor Project with WBS (Work Breakdown Structure) lines. The project status workflow differs between weclapp editions (Services vs Trade); we map the source status to the corresponding Infor project phase. Time entries transfer as labor transactions against the project WBS. Sub-task hierarchies require flattening into WBS structure during transformation.

weclapp Documents attached to Customers, Orders, Invoices, and Projects export as binary blobs with original filenames. We re-upload to Infor IDM or attach via ContentDocumentLink to the parent Business Partner, Order, or Project record. Link integrity is preserved where the destination supports the same parent-child relationship; otherwise documents are attached to the closest available parent entity and flagged for admin review.

weclapp allows custom fields on most objects but has no unified custom-field registry. We enumerate active custom fields per object during discovery by querying object metadata. Custom field values transfer as key-value pairs into Infor custom fields of matching type (text, number, date, picklist). Fields with no Infor equivalent are flagged for manual re-entry or configuration as a new Infor custom field before migration.

weclapp Users map to Infor User records and to Owner fields on transactional records. We resolve by email match against the Infor destination. Inactive weclapp users are excluded from the migration user set. Active user count in weclapp affects licensing but does not need to match Infor user count 1:1; we flag any Owner references without a matching Infor User for admin provisioning before record import.

Helpdesk Ticket is only available on weclapp plans with the Helpdesk module activated. If the module is absent, we warn the customer that tickets are not present in the export and adjust scope accordingly. If active, tickets transfer with linked Customer, status, priority, and conversation threads. Infor CloudSuite uses Infor OS Service Management or requires FSM integration; we flag the destination service module configuration as a prerequisite.

Contract Management add-on records transfer if the module is active on the source plan. Contract details and linked documents migrate; the contract workflow state requires manual re-entry or configuration in Infor's contract lifecycle management module. Contracts without an active add-on are out of scope and cannot be recovered from the export.