A Drupal Config Sync Preflight Checklist Before Production Deploys

Before importing Drupal configuration on production, verify that the configuration you are about to import matches the environment you are deploying to. Most config sync incidents come from small mismatches: a split is inactive, ignored config is not actually ignored, a module was removed from code but remains in configuration, or editors changed Webforms and blocks directly on production.

Minimum preflight

• Confirm the expected Config Split is active for the target environment.
• Confirm Config Ignore rules protect live-managed Webforms, custom blocks, and environment values.
• Compare active config to sync config before running the import.
• Check core.extension against installed code before importing.
• Export a machine-readable report into CI artifacts.

What to do when a warning appears

Do not treat every warning as a deployment blocker. Treat it as a decision point. A warning may mean the team should export production config first, adjust ignore rules, enable a split, install a missing module, or explicitly accept a known difference.

Vamao Drupal Config Guard OS automates these checks and turns the result into a risk report that developers, release managers, and clients can understand before a deployment starts.