Migrate from Stride ERP to Acumatica

Stride's flat Customer record — which mixes company name, primary contact email, and billing address — splits into Acumatica's BusinessAccount (company-level: account ID, name, class, status) and a child Contact (individual: name, email, phone, title). The Stride customer type field determines whether BusinessAccount.ClassID maps to a customer or vendor class in Acumatica.

Vendors map 1:1 to Acumatica APVendor. Stride's vendor address and payment terms fields map to Vendor.VendorID, VendorName, and the PaymentSettings branch. Stride vendor contacts become child Contact records linked to the Vendor record via the ACRContact junction table. Default vendor class and tax zone settings are assigned from Stride's vendor type field, and payment term lookup uses the Acumatica PaymentTermID list for the target tenant.

Employee records map to Acumatica Employee with Stride's employee ID, name, email, department, job title, and employment status. Stride department names map to Acumatica Department records where they exist; otherwise they create as new departments. Active / inactive status on Stride's employee record sets the Employee.IsActive flag in Acumatica.

GL accounts map 1:1 to Acumatica Account records. The account number, name, and type (Asset, Liability, Equity, Revenue, Expense) transfer directly. Acumatica requires accounts to be scoped to a Company — we assign accounts to the target company during schema setup. Sub-accounts in Stride map to Acumatica's Subaccount dimension if Stride uses hierarchical account coding.

Stride's Products object splits by inventory tracking flag: products with inventory tracking enabled migrate to Acumatica InventoryStockItem with warehouse and quantity fields; products flagged as non-tracked migrate to NonStockItem with description and cost only. Stride's product category maps to Acumatica's Inventory Item Class (ItemClassID) which controls the default posting account and UOM schedule.

Stride product categories map to Acumatica ItemClass records. The ItemClass controls default stock item settings including posting accounts, land cost, and valuation method. Category descriptions in Stride migrate as ItemClass.descr for audit reference. We create ItemClass records before importing StockItems so the ItemClassID foreign key resolves on load.

Stride Projects map to Acumatica PMProject with project ID, name, status, customer link, start date, and end date. The Stride project status (Active / Completed / On Hold) maps to PMProject.Status (Active / Completed / Planning). Project cost budget fields from Stride map to PMProject.BudgetedCosts if the source captures them; otherwise budget is configured post-migration in Acumatica's Project Budget screen.

Each Stride project task maps to a PMTask under the corresponding PMProject. Task name, description, start date, due date, and status transfer directly. Stride's task assignment (team member) maps to PMTask.RateTableID and the employee link. Task-level notes from Stride become PMTask.descr. If Stride uses a task hierarchy (parent / child tasks), we replicate it in Acumatica via PMTask.TaskID nesting.

Stride sales orders map to Acumatica SalesOrder. Order number, customer reference, order date, status, line items (product, quantity, unit price), and total amount transfer directly. The Stride warehouse location maps to SalesOrder.ShipToBranchID. Unreleased orders in Stride post as SalesOrder with status On Hold in Acumatica so the Acumatica admin can review before approval.

Stride invoices split by type: customer invoices become ARInvoice records linked to the BusinessAccount; vendor bills become APInvoice records linked to the Vendor. Invoice number, date, due date, description, and total transfer as document-level fields. Stride line items (description, quantity, unit price, discount) map to ARTran and APTran lines with the corresponding inventory link.

Stride add-on packages (Fleet Management, Document Management, Learning Management) store data in custom Stride tables. We map these to Acumatica by creating custom DAC fields ( dacAttributes ) on the nearest standard screen — for example, Stride fleet vehicle records become a custom VehicleMileage DAC linked to Equipment. Custom module metadata is exported as a JSON specification for Acumatica developer configuration.

Files attached to Stride records (invoices, projects, products) are downloaded and re-uploaded to Acumatica as NoteDoc attachments linked to the migrated record. File size limits of 25MB per file in Acumatica apply. Files without a matching record in Acumatica are staged in FileStorage and linked to a reference note for manual assignment.