Migrate from Adaptive to Acumatica

Adaptive GL accounts map 1:1 to Acumatica accounts. The account number and description copy directly. The subaccount code must be added in Acumatica — this is where Adaptive's cost-center, location, and custom dimension values land. We export the full account list with all dimensional tags and generate the subaccount segments during the account-structure design phase before any data loads.

Adaptive cost centers map to one or more subaccount segments in Acumatica. If Acumatica's subaccount mask uses a single-segment structure, all Adaptive cost-center values land in one segment. If the mask uses multiple segments (for example, Entity + Department + Project), we map Adaptive cost center to the appropriate segment and use custom fields or additional segments for the remaining dimensions.

Adaptive location values split into Acumatica branch records (if your Acumatica configuration uses Branches for legal-entity or site-level tracking) and a subaccount segment. For reporting that requires location-level P&L, we assign each Adaptive location to both a branch and a subaccount segment so both Acumatica's report designer and generic inquiry can slice by location.

Adaptive custom dimensions beyond cost center and location (for example, a Revenue Category or Product Line dimension) map to additional subaccount segments if your Acumatica subaccount mask has available segments. If all segments are consumed, we map the dimension to a custom field on the journal entry (GLTran) and include it in the import template. We surface the available segment count during the account-structure design phase.

Adaptive customer records migrate as Acumatica customer records. The Acumatica customer record requires a LocationID — if Adaptive tracks a primary address per customer, we use it as the default location. Additional addresses in Adaptive migrate as additional CustomerLocation records in Acumatica. Customer balances migrate as open AR amounts via journal entry or AR invoice import.

Adaptive vendor records map to Acumatica vendor records. The primary address migrates as the default vendor location. Additional addresses in Adaptive migrate as additional VendorLocation records. Vendor open balances migrate as AP amounts via journal entry or AP bill import.

Each Adaptive journal entry line carries an account code plus cost-center, location, and custom dimension references. We resolve the full subaccount code for each line using the account-structure map built during the design phase. Dimension values without a subaccount mapping are flagged before the migration runs and assigned to a default segment or custom field. The journal entry date, description, and amount migrate directly.

Adaptive planning versions and scenarios (Budget, Forecast, Actuals, What-If) have no native Acumatica equivalent. Acumatica manages budgets as GL entries or budget journals scoped to a fiscal period. We export all Adaptive version data including assumptions, drivers, and linked formula values as structured reference records. Your Acumatica admin uses these to rebuild budget versions as budget journal entries per fiscal year.

Adaptive currency and exchange rate tables export as-is. Acumatica maintains its own exchange rate table (Configuration > Cash Flow > Exchange Rates). We map Adaptive rate dates and values to the Acumatica exchange rate table. For multi-currency Adaptive setups, Acumatica's currency module is activated and configured before journal entry migration begins.

Adaptive department hierarchy maps to Acumatica's organization tree (if using the Organization feature for branch-level consolidation) and/or to a subaccount segment. We prefer the organization tree when the Adaptive department structure reflects legal entities or subsidiaries, and the subaccount segment when it reflects cost-center accountability. The preference is confirmed during the account-structure design phase.

Adaptive attachments on journal entries or accounts are downloaded and re-uploaded as Acumatica notes or files on the corresponding record. File size limits of 25MB per file apply in Acumatica. Files attached to journal entries are stored on the journal entry record itself using Acumatica's file management.

Adaptive users are resolved by email match against Acumatica contacts. If an Acumatica user does not exist for the Adaptive user's email, the record is flagged as unresolved before migration. Your Acumatica admin either invites the user first or assigns the record to a fallback owner. No financial record lands without an owner assigned.