Migrate your Jeeves ERP data

Jeeves stores a hierarchical chart of accounts covering balance sheet and P&L structures. We map account codes, names, and account types directly into the destination ERP's COA, preserving the full account tree and any currency assignment per account.

Customer records in Jeeves include contact details, billing/shipping addresses, credit limits, and payment terms. We migrate customer master records 1:1, mapping to the destination's equivalent customer/vendor object and preserving any custom fields defined on the Customer form.

Vendor master records in Jeeves mirror the customer structure with supplier-specific fields. We map Vendors to the destination's vendor object, preserving payment terms, bank details, and multi-currency settings per vendor.

Jeeves Items cover both products and materials with BOMs, routing, cost layers, and UoM settings. The level of detail varies by edition. We migrate Items preserving BOM structures and cost data, but custom item-specific fields require field-level mapping against the destination schema.

Outstanding payables and receivables are standard ledger documents in Jeeves. We map open invoice records with full line-item detail, due dates, and amounts, leaving only closed documents as historical records.

Jeeves stores transaction history at the ledger level. Volume of historical records can be large. We scope historical transactions with the customer during planning, applying date-based filters and chunked exports to avoid API timeouts on high-volume ledgers.

Journal entries in Jeeves carry a date, description, and debit/credit lines with account assignments. We preserve journal entry numbering schemes and reversing entry flags where configured, mapping them into the destination's journal entry format.

Fixed assets in Jeeves include acquisition cost, depreciation schedule, and asset category. Depreciation methods vary by country localization. We migrate the asset master and current book values, and flag whether accumulated depreciation is held as a separate ledger entry in the destination.

Jeeves user records include role assignments, team memberships, and permissions. We migrate user accounts as employee records or system users in the destination, but role mappings are destination-specific and must be defined per customer.

Jeeves Projects support time tracking, expense recording, and resource assignments. We map project records with associated tasks, milestones, and time entries into the destination's project management or PSA module, preserving project status and budget data.

Order documents in Jeeves carry header and line-item detail with delivery schedules and pricing. We migrate open orders preserving line items, quantities, and delivery dates, typically as draft or pending records to be confirmed post-migration.

Manufacturing BOMs and routing definitions are core Jeeves objects. We map BOM structures and work center assignments, but multi-level BOMs and alternate routings require careful sequencing to avoid circular reference errors in the destination.

Jeeves supports document attachments on most business objects. We export attachments as binary blobs and re-associate them to the migrated parent record in the destination. Large attachment volumes increase migration time significantly.

Jeeves process-based automation engine defines customer-specific workflows that are tightly coupled to the instance's configuration. We do not migrate automation rules as executable logic; these must be rebuilt in the destination system by the customer's implementation team.