Migrate from Breeze ERP to Acumatica

Breeze Projects map directly to Acumatica PMProject records. We preserve the original Breeze project name, description, status, start/due dates, and estimated hours as PMProject fields. Breeze task hierarchies become PMTask sub-records under the project. Custom fields on the Breeze project map to Usr-prefixed fields on PMProject via Acumatica DAC extension.

Breeze Tasks under a project map to PMTask sub-records in Acumatica's Projects module. Each task inherits the PMProjectID from its parent Breeze project. Task name maps to summary, description maps to the detail field, and priority maps to PMTask.urgencycd with value conversion. Breeze status (To Do, In Progress, Done) maps to PMTask.status with Acumatica-specific status codes.

Breeze team members resolve to Acumatica Contacts by email match. The Contact.FullName maps from Breeze user display name, and Email maps directly. Unmatched Breeze users are flagged before migration — you either create Acumatica user accounts first or assign those records to a fallback Contact. Breeze user IDs are stored as a custom reference field for owner traceability.

Breeze project-level custom fields map to Acumatica PMProject extension fields with Usr-prefixed names. Type-aware mapping: text → string(256), number → decimal, date → date, picklist → selector. Each field requires an Acumatica Customization Project to define the DAC extension and publish it before data loads. FlitStack delivers the field-definition mapping plan as part of the schema setup package.

Breeze task custom fields become Acumatica PMTask extension fields (Usr-prefixed). Acumatica requires the DAC extension to be published in a Customization Project before PMTask records with those fields can be inserted. FlitStack sequences the migration so custom field definitions are deployed first, then PMTask data loads. Picklist fields from Breeze require value-by-value mapping against Acumatica selector definitions.

Breeze task priority (Low, Medium, High) maps to Acumatica PMTask urgency codes using value translation: Low → Urgency 2 (Low), Medium → Urgency 3 (Medium), High → Urgency 4 (High). Urgency code defaults (Urgency 1–4) are defined in Acumatica's Priority code table. If your Acumatica instance uses custom urgency codes, we map against your actual code values.

Breeze task status (To Do, In Progress, Done, Cancelled) maps to Acumatica PMTask.status codes. Acumatica's default Project Task statuses are New, In Progress, Completed, and Cancelled — we map each Breeze status to the closest Acumatica equivalent. Breeze CompletedDate maps to PMTask.dateCompleted where applicable. If Breeze uses custom task statuses, we produce a full value-mapping table during the planning phase.

Breeze estimated hours on a task map to PMTask.estimatedHours. This field is available on PMTask and enables Acumatica's project budget vs. actual reporting. If Breeze stores estimated hours at the project level rather than the task level, those map to PMProject.estimatedDuration or a custom field on PMProject depending on your Acumatica configuration.

Breeze actual logged hours become Acumatica ProjCost labor items linked to the PMTask. Each Breeze time-entry maps to a ProjCost record with the employee as the cost code, hours as the quantity, and the task's labor item as the inventory ID. This preserves individual time entries as cost transactions rather than collapsing them into a single aggregate figure.

Breeze file attachments on tasks download and re-upload as NoteDocuments in Acumatica, linked to the corresponding PMTask or PMProject. File name and the original upload timestamp are preserved as note attributes. Acumatica's default file size limit is 25 MB per file; files exceeding this are flagged for manual handling or chunked upload.

Breeze allows multiple tags per project. Acumatica PMProject uses a single classID field for classification. The primary Breeze tag maps to classID; additional tags are stored in a custom multi-select field (UsrBreezeTags__c) or as a related note. We surface the tag mapping plan before migration so you can decide whether to consolidate tags into a single classID or use the custom multi-select approach.

Breeze's internal project ID is stored as a custom text field (UsrBreezeProjectID__c) on PMProject. This serves as the source system reference for delta-run de-duplication, reconciliation audits, and rollback identification. It is required for the delta pickup window to work correctly — new or modified Breeze records are matched against this ID during the final sync pass.