IntegrationHub ETL vs. Transform Maps for CMDB Tables in Foundation Data Sync(FDS)Foundation Data Sync Data transformation of CMDB & Non CMDB tables in FDS Transform Maps vs. IntegrationHub ETL — Feature Behavior & Analysis 1. Purpose This article explains how the FDS (Foundation Data Sync) application determines which method to use when transforming data in a target ServiceNow instance. This article provides a clear understanding of when Transform Maps are used versus IntegrationHub ETL pipelines and the implications of each choice. 2. Feature Overview — How FDS Decides the Transformation Method The Offering item form includes two key fields that control how data transformation is performed: 2.1 Decision Logic The following table summarizes the decision logic applied by the FDS application: Table Type Maintain SysID Method Used SysID Behavior CMDB Table Checked (True) Transform Map Preserved CMDB Table Unchecked (False) IntegrationHub ETL New SysID assigned Non-CMDB Table Checked (True) Transform Map Preserved Non-CMDB Table Unchecked (False) Transform Map New SysID assigned 3. Transform Maps vs. IntegrationHub ETL — Feature Behavior & Impact Each method has distinct strengths and limitations. The following sections provide a comprehensive comparison to help teams understand why FDS makes these choices and what implications each has for data governance, system integrity, and operational effort. 4. Recommendations & Best Practices Always check Maintain SysID when synchronizing CMDB tables if you need the source and target instances to stay in perfect alignment.Use IntegrationHub ETL only for CMDB tables when SysID consistency is not a concern — for example, in a fresh target environment where no existing references to the source SysIDs exist.For all non-CMDB tables, FDS automatically uses Transform Maps. No additional action is needed by the user.Before enabling synchronization on CMDB tables, consult with your ServiceNow platform team to understand the relationship dependencies of the records involved.Monitor import set logs and Transform Map run history to detect any mapping or coalesce issues during data transfer.Use case of maintaining SysId across instances A server record with SysID = ABC123 on the source instance links to software records, incidents, and change requests. Synchronizing via Transform Map retains this SysID on the target, preserving all relationships without manual re-mapping.If they are not preserved, the ETL on target creates a new record with a different SysID (e.g., XYZ789), breaking references to the original SysID (ABC123) and causing data inconsistencies. In this case, a transformation is required in ETL to identify the record. 5. Glossary and Important links 1. Transform Maps documentation 2. IntegrationHub ETL documentation 3. IntegrationHub ETL introduction (community link)