Migrate from Guardian Software to Acumatica

Guardian organizations serve both customer and vendor roles depending on business relationships. FlitStack splits them into Acumatica Customers and Vendors based on a role flag in Guardian's organization record. If an organization has both customer and vendor roles, two separate records are created in Acumatica with the same name and address details to maintain data integrity across both entities.

Guardian contacts map directly to Acumatica Customer Contacts (Contact table with CustomerID populated). The primary contact flag from Guardian becomes the IsPrimaryContact checkbox in Acumatica. Email addresses, phone numbers, and job titles transfer verbatim without transformation.

Guardian user accounts are resolved to Acumatica Employees by email address matching. Active Guardian users become Active Employees in Acumatica; archived users are set to Inactive with a Note attached referencing their Guardian status for audit purposes. Unmatched Guardian users are flagged before migration for team assignment decisions.

Guardian cases map to Acumatica CRM Cases (CRCase). The Guardian case number becomes the Acumatica CaseID; the Guardian description maps to Subject. Resolution status, priority, and assigned employee carry over. Original create and close timestamps are preserved in custom datetime fields.

Guardian production work orders require a decision: if they represent manufacturing orders, they map to Acumatica Production Orders with BOM and物料 links. If they represent job-cost tracking, they map to Projects with task-level cost tracking. Your team selects the strategy during the sample migration review.

Guardian inventory parts map one-to-one to Acumatica Inventory Items. The Guardian part number becomes the Inventory CD; description maps to Description field. Unit of measure conversions are applied automatically if Guardian and Acumatica UOM lists differ during the migration load.

Guardian purchase orders migrate to Acumatica PO Orders without structural changes. Line items map to POLine with inventory item links where applicable. Open and closed status carries over; closed orders retain their historical totals for financial reporting continuity.

Guardian sales orders map to Acumatica Sales Orders (SOOrder). Customer links resolve via the Organization-to-Customer mapping. Line items map to SOLine with identical item, quantity, and unit of measure specifications from the source Guardian record.

Guardian custom properties on organizations that have no direct Acumatica equivalent (e.g., foundry-specific classification codes) become Usr-prefixed custom fields on the Customer DAC. Field type is matched: text to string, pick-lists to combo boxes, numbers to integer or decimal fields.

Guardian contact-level custom properties without a direct Acumatica analogue are migrated as Usr-prefixed fields on the CustomerContact data access class. The field definition is created during the schema setup phase before any data loading begins to ensure proper field creation and data integrity.

Guardian file attachments are downloaded and re-uploaded to Acumatica's Files system (NoteDoc), linked to the parent record (Customer, Contact, or Case) by Entity and RecordID. File name, MIME type, and upload date are preserved. Inline images in notes are extracted and re-hosted.

Guardian activity records (calls logged, email threads, internal notes) map to Acumatica CRCaseActivity entries attached to the corresponding Case. Original timestamps and assigned user are preserved. Activities without a linked case are attached to the Contact record as a general Note.

Guardian Process Designer configurations do not have a direct Acumatica equivalent. FlitStack exports workflow definitions as a structured JSON file and human-readable summary. Your Acumatica administrator uses Business Events and Automation Schedules to rebuild the workflow logic manually.

Guardian system-level configuration such as routing rules, notification templates, and SLA definitions is exported as a reference CSV file. Acumatica handles these through separate screens including SLA Definitions, Notification Templates, and Workflows, which must be rebuilt manually after migration.