Migrate your Guardian Software data

Standard customer and account records with address, contact details, and classification by customer type. We map these directly to the equivalent account or customer object in the destination ERP.

Core manufacturing transaction in the foundry context. Includes order status, quantity, schedule dates, and routing to specific work centers. These map cleanly to Jobs, Work Orders, or Production Orders in destination systems.

Raw materials, alloys, and finished castings tracked by location and bin. Inventory balances, reorder points, and unit-of-measure conversions are standard fields we handle via mapping tables.

Inspection results, non-conformance reports, and certificates of conformance. The schema supports attachments and linked test data. We map quality codes and disposition statuses to destination quality objects; any custom inspection fields require field-level mapping.

Machines, furnaces, and tooling assets with maintenance schedules, depreciation data, and location assignments. Asset master records transfer as full objects with standard financial and operational fields preserved.

Step-by-step routing of production orders through work centers with labor hours, machine hours, and sequence. Routing structures vary by foundry process type, so we validate step count and cycle-time estimates against destination routing templates.

Engineering drawings, batch sheets, and compliance certificates stored as file attachments. We export documents alongside their parent records and re-associate them in the destination system. Filename and metadata mapping depends on the destination's document management conventions.

User accounts with role-based access control. Role names and permission sets vary between Guardian and the destination; we map role hierarchies but recommend a post-migration access review to align with target system permissions.

Account codes and cost-center structures for financial integration. Foundry-specific cost pools (scrap, rework, tool wear) require account-code mapping to ensure GL continuity in the destination.

Guardian supports user-defined fields on standard objects for foundry-specific tracking. Custom field names, data types, and picklist values are extracted and mapped; complex formula fields may require post-migration validation.

Historical journal entries for cost accounting and period closes. We extract entry headers and line items; reversing entries and adjustment flags are preserved where supported by the destination schema.

Open and closed PO headers with line items, quantities, prices, and vendor assignments. Vendor cross-references are remapped to match the destination's vendor master.