Altium DISCUSSION

What should be reviewed when moving an older Altium project to Constraint Manager?

Started by jen19 Altium migrationConstraint Managerlegacy rulesPCB reviewconstraint scope
3 replies 248 views 4 participants
Latest activity · 27 Sep 2026

What should be reviewed when moving an older Altium project to Constraint Manager?

jen19 Altium Forum
#1

Altium supports both older rule-management workflows and Constraint Manager projects. What checks would you make when migrating an existing board rather than creating a new project?

The board already contains custom clearances, differential pairs and a few intentional exceptions. How can the team detect a change in rule scope before it affects the next revision?

Reference: Altium: Constraint Manager (https://www.altium.com/documentation/altium-designer/sch-pcb/constraint-manager).

Community replies 3

Re: What should be reviewed when moving an older Altium project to Constraint Manager?

#2

Archive the original project and record a baseline DRC report before migration. Inventory the important custom rules, their scope and their rationale, including accepted exceptions. Preserve a set of manufacturing outputs from the baseline as a separate artifact. That gives you something concrete to compare if the new constraint workflow reports different results.

Re: What should be reviewed when moving an older Altium project to Constraint Manager?

#3

Inspect representative nets, pairs, rooms and special pads after conversion. Test both an ordinary case and an intentional boundary violation on a disposable copy. If a clearance was meant to apply only between two classes, confirm that both classes and their membership survived. A rule with the correct numerical value but the wrong scope can be more misleading than a missing rule.

Re: What should be reviewed when moving an older Altium project to Constraint Manager?

#4

Compare the resulting reports and review any changes instead of suppressing new warnings to recreate the old count. Confirm which workflow the project actually uses and that the reviewer has permission to edit its constraints. Finish by saving the migrated project, reopening it and checking that the intended settings persist. Document the migration as a design-tool change in the revision history.

TEP COMMUNITY