Migrate your ERP Mark 7 data

Customer records are standard with address, contact details, and payment terms. No known schema drift between instances. We map them directly to the destination Customers or Accounts object.

Vendor records follow the same structure as Customers with the addition of 1099 settings and W-9 status fields. We preserve these as native fields in the target.

Items represent products, raw materials, and services. ERP Mark 7 allows custom properties per item type (inventory vs. non-inventory vs. service). We map item types and custom fields to the equivalent destination object and flag any that cannot be matched.

The COA structure is configurable per company. We map standard account numbers and names directly but flag any non-standard segment configurations that require manual re-creation in the target ERP.

Open receivables and payables require careful sequencing—paid status, aging buckets, and payment method must all be carried through. We chunk these by invoice date and payment status to avoid duplicate posting.

Transaction history can be migrated as journal entries or as line-item records depending on the destination system's capability. We flag the chosen strategy during scoping and handle year-end closes as separate batches.

Work orders link Items to BOMs and routing steps. Custom fields on work orders (e.g., machine center, priority flags) require explicit mapping to destination equivalents or custom fields.

Documents are stored as attachments to transactions, items, or customers. We export them in their native format and re-attach them to the corresponding records in the target. Binary attachments are chunked by parent object to stay within file-size limits.

ERP Mark 7 allows user-defined fields on most standard objects. We discover the full custom property set during the schema audit phase and map each to a corresponding field in the destination or create a custom field there.

User records include name, email, role, and department assignment. Role names do not map 1:1 to other ERPs, so we match by permission level and flag roles that need manual reassignment.

Tax codes are region and product-category specific. We map active tax codes and flag any deprecated or jurisdiction-specific codes that cannot be replicated in the destination.

Departments map to cost centers or locations in most destination systems. ERP Mark 7 allows nested department hierarchies which we flatten or preserve based on the target's capability.