Migrate from Logo Go to Infor CloudSuite Corporate

Logo Go Chart of Accounts records export as account codes, descriptions, and account types from the application's database. These map to CloudSuite's CoA structure with account codes preserved as the primary identifier. Multi-segment account codes (e.g., 4-2-1 for a revenue sub-account) require decomposition and mapping to CloudSuite's account hierarchy. We flag any inactive or blocked accounts that should not carry forward.

Logo Go customer records map to CloudSuite Customer (or Business Partner depending on the CloudSuite industry template). We extract customer name, address, tax ID, payment terms, credit limit, and AR account assignment from the source database. Customer addresses are decomposed into CloudSuite address fields (Address1, Address2, City, State, PostalCode, Country). Tax ID becomes the Tax ID on the Customer form.

Logo Go vendor records map to CloudSuite Vendor with the same field decomposition as customer records. Vendor payment terms, bank account details, and AP account assignments migrate. We flag any vendor records with missing or invalid tax IDs because CloudSuite's tax validation may reject these during AP invoice entry.

Logo Go item records map to CloudSuite Item Master (or Product depending on the CloudSuite module). Item code, description, unit of measure, cost, and price lists migrate. We extract the base UOM code and any alternate UOM conversions from Logo Go's item definition. BOM and routing data, if present in Logo Go, maps to CloudSuite Bill of Materials and routing tables with a separate configuration pass.

Logo Go open AP records (unpaid invoices and vouchers) migrate to CloudSuite AP records with vendor lookup resolved from the Vendor mapping. Invoice number, invoice date, due date, amount, and distribution lines carry forward. We flag any AP records with inconsistent vendor assignments or missing distribution lines for manual reconciliation before final migration.

Logo Go open AR records migrate to CloudSuite AR invoices with customer lookup resolved from the Customer mapping. Invoice number, invoice date, due date, amount, and distribution lines carry forward. Partial payments already recorded in Logo Go are preserved as payment history linked to the invoice.

Logo Go journal entry headers and lines require sequencing: headers must exist before lines can be entered in CloudSuite. We extract entry number, date, description, and the full line set (account code, debit, credit, reference). Only posted and approved journal entries are candidates for migration; draft or unposted entries require posting in Logo Go before extraction. This is flagged explicitly during scoping because many Logo Go installations have unreconciled draft journal entries.

Logo Go fixed asset records map to CloudSuite Fixed Asset with asset number, description, acquisition date, acquisition cost, accumulated depreciation, useful life, and depreciation method. We flag assets that have not been fully depreciated but have no active depreciation schedule in the source. Depreciation convention must match CloudSuite's fiscal year configuration.

Logo Go stores tax codes and rates in region-specific tables that vary by country. We extract every distinct tax code, rate, and applicability rule from the source database and map them to CloudSuite's tax parameter forms. Multi-jurisdiction tax setups (VAT + sales tax + withholding) require separate tax codes in CloudSuite, one per applicable rule. This mapping is complex and requires a tax consultant review before migration.

Logo Go custom fields are application-specific database extensions that do not have a standard export format. We identify every custom column added to the standard Logo Go tables (Customer, Vendor, Item, GL Account) during scoping, document their data types, and create equivalent custom fields in CloudSuite using the Mongoose framework. Data values migrate as part of the parent record migration once the CloudSuite custom field schema is deployed.

Logo Go user records map to CloudSuite User accounts. We extract user name, email, role, and warehouse/location assignments. Inactive users are preserved with inactive status in CloudSuite to maintain audit continuity. User passwords do not migrate; they must be reset via CloudSuite's password recovery process post-migration.

Logo Go warehouse and location records map to CloudSuite Warehouse. Warehouse code, name, address, and default settings carry forward. Item-warehouse assignments from Logo Go's inventory module map to CloudSuite's item-warehouse stocking records. This mapping is required before inventory transactions can be posted in CloudSuite.