Migrate from Base ERP to Infor CloudSuite Corporate

Base ERP Products (Offers in BaseLinker terminology) carry SKU, name, description, images, and dimensions. We extract these via CSV or REST export, chunk the catalog into batches of 500-1000 SKUs, and transform them into Infor CloudSuite Item Master records. The source SKU becomes the Infor Item_c field. Custom product fields from Base ERP are mapped to Infor user-defined fields via the Infor Data Catalog Generate from Sample Data workflow or the custom BOD mapping with XSLT. We flag any Base ERP products in beta-stage Inventory Control modules and defer their migration until schema stability is confirmed.

Real-time stock quantities per Warehouse per Product are stored as integer values in Base ERP. We pull a full stock snapshot at migration start time to capture a consistent point-in-time before live sync resumes. Each stock record is mapped to an Infor Item Warehouse record that combines the Item ID, Warehouse code, On Hand quantity, and reorder point. We resolve the Infor Location reference from the Warehouse mapping phase before inserting Item Warehouse records.

Base ERP organizes stock into named Warehouses. Multiple warehouses are supported but naming conventions vary widely between accounts. We map each source Warehouse to an Infor Location record using the Location ID, name, and address fields. Infor CloudSuite Industrial and Distribution use Location to track physical sites, zones, and bins for inventory costing and picking. We preserve the source Warehouse ID as a reference field for audit traceability.

Base ERP pricing can be defined per marketplace channel, per quantity tier, or via rule sets. The pricing object is a flat key-value structure in exports but may require expansion into per-channel price lists in Infor. We map each active pricing rule to an Infor Price Book entry or pricing formula, noting the customer segment, quantity break, and effective date. Complex rule sets that involve conditional logic require manual rebuild as Infor pricing formulas; we document each one in the handoff inventory.

Base ERP Orders carry customer details, line items, shipping address, payment method, and status. We export open and historical orders and map them to Infor CloudSuite Sales Order records. The Infor Sales Order inherits the Customer ID (resolved from the Customer mapping phase), the Ship-to Location, and the Order Date. Order lines map to Order Detail records with Item ID, quantity, and unit price. Completed orders include fulfillment tracking fields that map to Infor Shipment records.

Base ERP customer records are embedded in Orders rather than stored as standalone master records. We extract distinct customers from the order history, enrich them with any available contact fields (email, phone, address), and create Infor Customer records. For customers who are also suppliers, we create both Customer and Supplier records in Infor with the appropriate roles set.

BaseLinker connectors to eBay, Amazon, Allegro, and other channels store channel-specific listing IDs and account credentials. We export the connector configuration table (channel type, listing IDs, sync rules) so that the destination can be reconnected. API credentials (tokens, API keys) are non-exportable from Base ERP and must be re-entered manually at the destination. We document every channel-to-offer mapping so that Infor admin relinks listings to the correct Item Master SKUs after migration.

User accounts in Base ERP carry roles (Admin, Operator, Warehouse Manager). We map Users to Infor CloudSuite User records and preserve role assignments as custom properties. Infor OS manages user provisioning and role-based access control through its Identity and Access Management layer. We resolve owners by email match and flag any Base ERP owner without a matching Infor User for admin provisioning before record import resumes.

Base ERP users can define additional fields per product (e.g., custom dimensions, certifications, seasonal flags). These export as extra columns in the product CSV. We rename and type-cast them to match Infor user-defined field types. Infor CloudSuite supports extended data structures via the Data Catalog, which can generate custom BOD schemas from sample data or manual definition. We use Infor's Generate from Sample Data workflow to create matching field definitions before loading product data.

Invoice generation is not a core Base ERP module; it is typically handled by an external accounting tool integrated via BaseLinker. We do not migrate invoice records. Customers should export invoices from the external accounting tool directly. We flag the absence of invoice data in the migration scope during scoping so that the customer plans accordingly.