Migrate from VIENNA Advantage to Acumatica

Vienna Advantage stores all parties (customers, vendors, leads) as a single Business Partner record with a Role field (Customer, Vendor, Both). Acumatica splits this into a Customer or Vendor record plus one or more Contact records linked via the Contact (Business Account) relationship. The migration splits by BusinessPartnerRole value: Customer → Customer + Contact, Vendor → Vendor + Contact, Both → both entity types. Primary address becomes the Customer Address; additional addresses become Location records.

Vienna Advantage stores contact details (phone, email, job title, address) directly on the Business Partner record. Acumatica requires these as separate Contact records with a link to the Customer or Vendor. Each Business Partner record with contact data generates one Contact record; contact name fields split into FirstName and LastName using space delimiting. Multiple contact persons within one Business Partner require multiple Contact records created from repeating contact fields.

Vienna Advantage embeds billing and shipping address on the Business Partner. Acumatica stores addresses in a shared Address table referenced by Customer.AddressID and optionally by Location records for multiple sites per customer. The migration maps the primary address to Customer.AddressID and creates Location records for any secondary addresses, linking each Location to its corresponding warehouse or delivery point.

Vienna Advantage Item records with ProductType=Inventory map to Acumatica Stock Item (ItemType=ST). Non-inventory items (purchased-only, service items) map to Non-Stock Item (ItemType=NS) or Service Item (ItemType=SE) depending on the Vienna Advantage Item Type value. Item attributes like Units, ItemClass, and Tax Category map to Acumatica's Units, Item Class, and Tax Category fields directly.

Vienna Advantage stores a single warehouse assignment per item (default warehouse field). Acumatica maintains a separate ItemWarehouse record linking ItemID to WarehouseID with QuantityOnHand per warehouse. The migration creates one ItemWarehouse record per unique warehouse found in Vienna Advantage Item records, populating QuantityOnHand from the Item's current stock value. Multiple warehouse assignments in Vienna Advantage require multiple ItemWarehouse records.

Vienna Advantage GL Account records map 1:1 to Acumatica Account records (both use AccountCode + AccountName structure). The account type (Asset, Liability, Expense, Income, Owner's Equity) maps to Acumatica Account.Type via value mapping. Note: Acumatica enforces account code format validation—account codes must conform to the Chart of Accounts format defined in the company's Branch settings before accounts can be saved. The migration plan includes a format validation step.

Vienna Advantage Journal Entry records (with batch, date, description, and line items) map to Acumatica GL Journal Transactions. Each journal line maps AccountCode to AccountID, DebitAmount to Amount in the correct sign, and description to TransactionDescription. Acumatica requires a Batch record wrapping journal transactions; the migration creates one Batch per Vienna Advantage Journal Batch or date grouping. Historical journal entry totals must balance (debits = credits) before Acumatica will accept the batch.

Vienna Advantage Sales Order records map to Acumatica Sales Orders (SO301000) with OrderType determined by document type mapping. AR Invoice records map to Acumatica AR Invoice (AR301000). Line items map ItemID to InventoryID, Quantity and Unit Price map directly, and Subtotal/Tax/Total flow into the corresponding Acumatica document fields. Open orders migrate with status Open; completed orders migrate as Completed with invoice reference preserved.

Vienna Advantage Purchase Order records map to Acumatica Purchase Orders (PO301000) with OrderType determined by document type. Vendor Bills (invoices received) map to Acumatica AP Bills (AP301000). Line items map VendorItemCode to the vendor part number field and VendorID to the Acumatica VendorID lookup. Open purchase orders migrate with status Open; closed POs map to Receipt and Bill records.

Vienna Advantage Project records map directly to Acumatica PMProject records. Project Tasks map to Acumatica Task records under each Project. Resource assignments in Vienna Advantage map to ProjectEmployee records. Billing information (rate tables, billing rules) maps to Acumatica Billing Rules on the Project. Non-billable project cost codes in Vienna Advantage require mapping to the appropriate Expense code in Acumatica's account structure.

Vienna Advantage custom fields on Business Partner, Item, and Project records require pre-creation in Acumatica as part of a Customization Project. Custom fields must be named with the Usr prefix (e.g., UsrViennaFieldID) and published to the tenant before migration runs. FlitStack AI generates the Acumatica Customization Project XML from Vienna Advantage field metadata. Post-migration, the custom fields appear on the correct Acumatica screens as read-write fields.

Vienna Advantage's integrated DMS with document indexing and version history has no direct Acumatica equivalent. Acumatica stores files asAttachments on individual records (SO Invoice, AP Bill, Project, Customer). The migration exports Vienna Advantage DMS files, associates them with the corresponding migrated record by entity ID lookup, and re-uploads using the Acumatica file attachment API. File version history is preserved as metadata comments on the attachment record. OCR data from Vienna Advantage DMS is not transferable.