Migrate your MERCI data

MERCI stores customer records with address, contact, and lifecycle data. We map the primary customer record and flatten billing/shipping addresses into destination fields. Where MERCI uses custom customer types, we translate them to destination enum values during import.

Orders carry line items, pricing, and status. We map order headers and line items separately so that partial failures on individual lines do not block the entire order. Order dates and expiration logic may need re-mapping depending on destination date handling.

Invoices reference orders and carry payment terms. We preserve the order-to-invoice linkage by embedding source order IDs as custom fields in the destination. Open versus closed invoice status requires explicit mapping to destination workflow states.

MERCI Items include product and service variants with pricing tiers. We map item master records and their pricing schedules, noting that bundle and kit compositions must be expanded into destination component structures.

Account codes and names are mapped directly, but account types (asset, liability, equity, revenue, expense) must be verified against destination account type taxonomy, as MERCI uses a simplified five-type model.

Vendor records parallel customer records in structure. We map vendor contacts, payment terms, andbank account details, applying the same address-flattening logic used for customers.

Employee records in MERCI carry department, job title, and compensation fields. We map these to destination employee objects and flag any effective-dated compensation history that needs to be preserved as separate historical entries.

MERCI stores file attachments in a proprietary blob store with no public export endpoint. We cannot extract binary attachments via API or standard CSV exports. Customers must independently download files from the MERCI UI or request a direct database export.