What Data You Can Migrate
The following tables provides details of the attributes you can migrate for each object type and which tool you can use for the migration.
Items
| Data | Can Be Migrated? | Migration Tool |
|---|---|---|
| Item Header (Gen Info, Page Two, Page Three) | Yes | FBDI |
| BOM/Structure | Yes | FBDI |
| AML | Yes | FBDI |
| Revisions | Yes | FBDI |
| Attachments | Yes (only latest file version) | FBDI |
| Relationships | Yes | Web Services Relationship data isn't supported in FBDI. You must use web services to create relationships. |
| History | No | Export as PDF and attach to item. |
Changes
| Data | Can Be Migrated? | Migration Tool |
|---|---|---|
| Change Header (Gen Info, Page Two, Page Three) | Yes | FBDI |
| Affected Objects | Yes | FBDI |
| Redlines | No | Export as PDF and attach to item or change |
| Attachments | Yes (only latest file version) | FBDI |
| Relationships | Yes | Web services |
| Approval and History | Yes |
FBDI In ChangeOrderImportTemplate, use the tab EGO_CHANGE_HISTORY_INT for migrating the change history. Any validation will not be run during the import of the change history data. Note that this feature is applicable only if you opt in to the feature Track Affected Object Redlines and Other Updates on Changes. You can also export history to a PDF file and attach it to the change. |
| Workflow steps | No | Assign final status using FBDI; other steps and workflow history aren't migrated |
Manufacturer Parts
| Data | Can Be Migrated? | Migration tool |
|---|---|---|
| Manufacturer Part Header (Gen Info, Page Two, Page Three) | Yes | FBDI |
| Attachments | Yes (only the latest version) | FBDI |
| Relationships | No | Not supported |
| History | No | Not supported |
Manufacturers
| Data | Can Be Migrated? | Migration Tool |
|---|---|---|
| Manufacturer (Gen Info) | Yes | FBDI |
| Page Two, Page Three | No | Not supported |
| Attachments | No | Not supported |
| Relationships | No | Not supported |
| History | No | Not supported |