Migrate from Atlas ERP to Infor CloudSuite Corporate

Atlas stores the COA as a hierarchical MS SQL table with account codes, names, types, and optional cost-center linkage. We extract the full account tree via direct SQL read and remap account codes to Infor CloudSuite's account structure during load. Multi-segment account codes (if used in Atlas) are flattened or segmented per Infor's chart-of-accounts configuration. The holding-company inter-company accounts are flagged for mapping to Infor's inter-company transaction configuration.

Atlas auto-posts all module transactions (Sales, Purchasing, Warehouses, Production, Payroll) to the Finance module. We extract journal_headers and journal_lines together and suppress auto-posting on the destination during the operational load phase, then import journal entries only for the open period after go-live to prevent duplicate ledger rows. Closed-period journals are exported as reference records only unless the customer requires full historical carry-forward.

Atlas Warehouses are master-data records with warehouse_id, name, address, and optional cost-center linkage. We export them as-is and create corresponding inventory locations in Infor CloudSuite. Multi-warehouse configurations (if Atlas uses site-based costing) map to Infor's site-level inventory organization with inter-warehouse transfer rules configured post-migration.

Atlas Items include product masters with BOM linkages for manufactured goods. The bom_lines table is separate from the item master and must be joined during extraction to preserve the BOM hierarchy. We export the item master, all bom_lines referencing each item_code, and routing_steps (production order routing definitions) as a joined package, mapping to Infor CloudSuite's Item Master and Bill of Material structure with quantity-per and operation-step sequencing preserved.

BOMs for manufactured items in Atlas live in a companion bom_lines table joined by item_code, not in the item master itself. A naive export of just the item master will miss all production capability. We extract the bom_lines and routing_steps tables alongside the item export, preserve the bill of material header and line structure with quantity-per and scrap-percentage, and map them to Infor CloudSuite's BOM and routing tables with multi-level BOM explosion preserved.

Atlas Production Orders link to the Production Planning module and carry a status lifecycle (planned, released, in-progress, closed). We preserve the order header, all routing steps referencing the production order, consumed and issued quantities, and co-product/by-product output lines. In Infor CloudSuite Industrial, production orders are created against the Item Master BOM and routing; we resolve the destination Item Number and Work Order Number during migration and flag any orphaned production orders that reference items not yet migrated.

Atlas Sales Orders are stored with a header and line table covering item_code, quantity, price, discount, and Responsible person. We extract the full order header, line detail, and associated customer record, preserving open/closed status, order dates, and pricing. In Infor CloudSuite, Sales Orders are created against the Customer and Item Master; we resolve customer_id and item_code references at migration time and flag any orders referencing unmigrated customers or items for manual review.

Atlas Purchase Contracts and planned deliveries are stored in the Purchasing module with contract headers, line items, supplier linkage, and delivery schedule dates. We export the full contract structure including pending delivery lines and map to Infor CloudSuite's Purchase Order or Blanket Agreement based on the contract type. Supplier records are resolved against the migrated vendor master; any unmatched suppliers go to a reconciliation queue.

Atlas CRM records include company name, contact persons, addresses, Responsible person, and lifecycle stage. We export the full contact hierarchy and map to Infor CloudSuite's Customer and Contact structure. The Atlas holding-company relationship (parent_company_id) is preserved as an Account hierarchy in Infor CloudSuite. Any custom CRM fields discovered via schema diff are mapped to Infor custom fields on the Customer or Contact object.

Atlas Employee records include name, department, position, employment status, and salary grade. We map these to Infor CloudSuite's HRM schema, preserving the department hierarchy and active/inactive employment status. Employee records that are tied to Infor-specific cost-center or payroll configuration are flagged for the customer's HR administrator to complete after migration because Infor payroll setup requires country-specific tax and benefit parameters not transferable from Atlas.

Atlas Payroll history is stored in a separate payroll module with period-based gross/net breakdown, deductions, and employer contributions. We export the run summary and line-by-line detail as reference data. Payroll configuration (deduction codes, tax codes, benefit plans) does not migrate because Infor CloudSuite payroll requires country-specific tax and benefit setup through Infor's payroll module. Historical payroll data is migrated as a financial reporting reference rather than as active payroll records.

User-defined fields added through Atlas's system administration module exist in companion tables or as extra columns not exposed in the standard UI. We detect these by running a pre-migration schema diff against the base Atlas table definitions, then include discovered extra columns in the export scope. Each custom field is evaluated for its Infor CloudSuite equivalent; simple text, number, and date fields map to Infor custom fields. Complex custom fields referencing lookups or computed values require manual mapping during the schema design phase.