Migrate from KeyedIn to Acumatica

KeyedIn Project maps to Acumatica Project with ProjectID, Description, status, start/end dates, and budget preserved. Acumatica requires branch and company assignment; KeyedIn projects lacking branch affiliation are assigned a default branch. Project status values (Active, Completed, On Hold) map to Acumatica Active/Completed/Hold status values.

KeyedIn Phases become top-level Tasks in Acumatica with TaskCD derived from the Phase name and Type='Project Default.' Sub-tasks in KeyedIn map to child Tasks under the phase-level Task. Each task row in Acumatica carries the ProjectID reference, Type, and its own WBSCode.

KeyedIn Tasks that are not phase-level become child Tasks in Acumatica under the parent phase Task. TaskCD and Description map directly. IsBillable and IsProdiction flags on the KeyedIn task carry forward to the Acumatica Task row. Parent relationships are established through the project-task hierarchy, ensuring each child task references the correct parent phase. Task-level attributes including budget and dates are preserved during the transformation where present in the source record.

KeyedIn Resource Allocations — which link a staff member to a project with hours, rate, and cost — become Project Task Detail rows in Acumatica. Each allocation generates one task detail row with EmployeeID, Date, DailyCapacity, BillableRate, and IsBillable. The many-allocations-to-one-employee pattern on a project collapses to one row per employee per task date.

KeyedIn Customer records (name, class, billing address, payment terms, credit limit) map directly to Acumatica Customer with CustomerID derived from the KeyedIn Customer ID or name. ClassID in Acumatica corresponds to the KeyedIn customer class; terms and credit limit carry forward. Customer locations in KeyedIn map to Acumatica Customer Locations (Address tab).

KeyedIn Vendor records (name, account number, terms, payment method) map to Acumatica Vendor with VendorID from the KeyedIn vendor identifier. Primary contact name, email, and phone transfer to the Vendor Contact screen. AP account assignment in Acumatica uses the default AP account or a mapped KeyedIn AP account field.

KeyedIn GL accounts map to Acumatica Accounts, but Acumatica requires branch-keyed subaccount assignments. We map the KeyedIn account segment to the AccountCD in Acumatica and derive Subaccount from a branch-mapping table (provided during discovery). Unmapped or inactive KeyedIn accounts are flagged for manual branch assignment before the migration commits.

KeyedIn Cost Centers have no direct Acumatica equivalent — they are organizational segments rather than GL accounts. We create a custom text or pick-list field (UsrCostCenter__c) on the Project and Task entities in Acumatica and populate it with KeyedIn cost center values. Cost-center-to-branch mapping is surfaced during discovery so the right branch assignment can override the custom field where appropriate.

KeyedIn Time Entries (employee, date, hours, project, task, description, billable flag) map to Acumatica Time Entries with EmployeeID resolved by email match to Acumatica Employees, ProjectID and TaskCD from the project migration, Date and TimeSpent preserved exactly, and Billable flag transferred. Timecard summary in Acumatica carries the approval status from KeyedIn if available.

KeyedIn Expense Reports and their line items (amount, category, project, task, date) migrate to Acumatica Expense Claims linked to the Project and Task. KeyedIn expense categories map to Acumatica Expense Codes via a value-mapping table. Receipt attachments from KeyedIn are re-uploaded as Files linked to the Expense Claim in Acumatica.

KeyedIn Inventory Items (item ID, description, unit of measure, cost, price, inventory warehouse) map directly to Acumatica Inventory Items. InventoryID is derived from the KeyedIn item identifier; UOM, LastCost, and ItemClass map. Items must land in Acumatica before any associated Manufacturing Order or Sales Order can reference them — we sequence this accordingly.

KeyedIn BOMs (parent item, component items, quantities, operation steps) map to Acumatica Bills of Materials. Components reference the migrated Inventory Items by their new Acumatica InventoryID — a mapping table links old KeyedIn item IDs to new ones. BOM revision levels in KeyedIn become revision codes in Acumatica BOMs.

KeyedIn Manufacturing Orders (MO ID, item, quantity, status, warehouse, operation dates) migrate to Acumatica Manufacturing Orders. Acumatica requires the manufactured Item to exist as an Inventory Item first — the inventory item migration runs as a prerequisite step. MO status (Open, Completed, Cancelled) maps to Acumatica Manufacturing Order statuses, and material issues/labor bookings are preserved as Operation Detail rows.

KeyedIn Purchase Orders (vendor, date, terms, line items with item/quantity/price) map to Acumatica Purchase Orders. VendorID, VendorRef, and terms carry forward. Line items reference the migrated Inventory Items and map vendor-specific unit costs. Open POs in KeyedIn land as Released POs in Acumatica; closed POs are migrated as Completed records for historical reporting.

KeyedIn Vendor Credits (credit memo issued by a vendor) map to Acumatica Vendor Refunds or AP Adjustments linked to the Vendor. The credit amount and description carry forward; GL lines are generated against the AP account. Credit applications to specific AP invoices are represented as payment applications in Acumatica if the original AP invoice was also migrated.

KeyedIn Sales Orders (customer, date, line items, warehouse) map to Acumatica Sales Orders with OrderNbr, CustomerID, and OrderDate preserved. Line items use the migrated Inventory Items; unit price and discount map from KeyedIn. Open orders land as Pending or On Hold in Acumatica pending warehouse confirmation.