Migrate from Masterplan to Acumatica

Masterplan customers map directly to Acumatica's Customer DAC. The primary address and contact email transfer as the default location and contact info. Masterplan's customer type (e.g., prospect vs. house account) translates to the CustomerClassID pick-list on the Acumatica Customer screen.

Masterplan vendors map to Acumatica's Vendor DAC. The Remit-to address and payment terms transfer as the default location. Masterplan's vendor type or category maps to the VendorClassID pick-list — we create matching class records in Acumatica before migration if none exist.

Masterplan stock items become Acumatica InventoryItem records. Item type (stock vs. non-stock vs. service) maps to the ItemType pick-list. The base unit of measure and any alternate UOMs transfer to the Units of Measure tab on the InventoryItem screen, allowing flexible measurement conversions in Acumatica's inventory management.

Masterplan warehouse-level inventory maps to Acumatica Warehouse records, with each Masterplan location becoming a LocationID record within the corresponding Warehouse. If Masterplan tracks bin or lot data, Acumatica's Lot/Serial class and Location class must be enabled before migration — we flag this in the pre-migration schema plan.

Masterplan projects map to Acumatica's PMProject DAC. The project type (Time and Materials, Fixed Price, etc.) maps to the TemplateID which drives the default Cost Code and Work Type structure. Each Masterplan cost category becomes a Cost Code in Acumatica's PM Cost Codes screen — we deliver a Cost Code mapping table before migration.

Masterplan cost categories transfer as PM Cost Code records linked to the destination Project template. Budget amounts per cost category map to PMBudget lines on the project. Rate-based cost codes require a corresponding Work Type with default hourly or unit rates configured in Acumatica.

Open Masterplan purchase orders map to Acumatica's PO303000 screen (Purchase Orders). Line items reference the migrated InventoryItem records by InventoryID. Taxes, terms, and shipping information transfer to the Details and Terms tabs. Closed POs migrate as historical records linked to the Vendor.

Open Masterplan sales orders transfer to Acumatica's SO301000 screen (Sales Orders). Customer and location links resolve via the migrated Customer records. Line items reference migrated stock items. Freight, discount, and tax fields map to their corresponding Acumatica fields by name.

Masterplan GL accounts require a manual cross-validation step before migration — Acumatica's chart of accounts segment structure is defined in Settings → Chart of Accounts. We deliver an account mapping spreadsheet that pairs each Masterplan account code with the corresponding Acumatica AccountCD. Closed or inactive Masterplan accounts are flagged for Acumatica deactivation after migration.

Masterplan custom fields on any entity map to Acumatica User-Defined Fields created via the Customization Project Editor (SM200505). We export the Masterplan custom field definitions (label, data type, pick-list values) and recreate them as UDFs on the corresponding Acumatica DAC before data loads. Large text or multi-select custom fields require verification that the UDF data type in Acumatica supports the same value range.

Masterplan project budget lines by cost category map to PMBudget records on the corresponding Acumatica project. Quantity budgets and amount budgets transfer separately. Revenue budgets for Fixed Price projects map to the Revenue Budget tab. Variance tracking between committed and actual costs uses Acumatica's built-in PM reporting.

Masterplan production orders and the associated material BOM and routing data do not have a direct Acumatica equivalent without the Manufacturing Edition active. We migrate production order headers and line summaries as reference records in a custom table; BOMs and routings must be rebuilt in Acumatica's Production BOM and Production Routing screens. If Manufacturing Edition is not licensed, these records are preserved as custom reference objects.

Masterplan user IDs resolve against Acumatica users by email address match. Unmatched owners are flagged before migration — your team either creates Acumatica user accounts first or assigns records to a fallback owner. Project managers and approvers with pending approval chains are migrated as Contacts with the OwnerID link populated where applicable.