Import / Export & Drift Detection

AlgoBridge lets you export your entire mapping configuration as a portable JSON file, import it to clone or restore a workspace, and detect when the live configuration has drifted from a saved baseline.

Exporting your configuration

Go to Settings → Import / Export → Export and click Download JSON.

The export includes all mappings — their Salesforce object names, PostgreSQL table names, sync direction, field list, external key fields, and write algorithm setting. It uses a Heroku Connect-compatible format so the file works with any tooling that understands that schema.

Via API:

curl -H "Authorization: Bearer sfbs_tok_xxxxxxxxxxxx" \
  "https://your-instance.example.com/api/v1/t/{workspaceId}/config/export" \
  --output config.json

What is and isn’t included

Importing a configuration

You can import a previously exported JSON file to:

• Clone a workspace — set up a staging environment with the same mappings as production
• Restore a configuration — roll back after an accidental mass-delete
• Migrate — move mappings to a new workspace or AlgoBridge instance

From the UI

1. Go to Settings → Import / Export → Import
2. Click Choose File and select your JSON export
3. Review the preview — AlgoBridge shows which mappings will be created and which will be updated
4. Click Import

AlgoBridge validates the JSON before applying it. If validation fails, the import is aborted and no changes are made.

Via API

curl -X POST \
  -H "Authorization: Bearer sfbs_tok_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d @config.json \
  "https://your-instance.example.com/api/v1/t/{workspaceId}/config/import"

Response:

{
  "success": true,
  "data": { "created": 3, "updated": 1, "skipped": 0 }
}

Import is additive by default — it does not delete mappings that exist in the workspace but are absent from the import file. To do a full replace, delete existing mappings manually first.

Drift detection

Drift detection lets you pin a point-in-time snapshot of your configuration (a baseline) and then compare the live configuration against it at any time.

This is useful for:

• Detecting unintended changes in production (e.g. a field was removed from a mapping)
• Auditing configuration changes since a known-good state
• Pre-deploy checks to confirm staging and production configs match

Saving a baseline

1. Go to Settings → Import / Export → Baseline
2. Click Save Current Config as Baseline

Via API:

curl -X POST \
  -H "Authorization: Bearer sfbs_tok_xxxxxxxxxxxx" \
  "https://your-instance.example.com/api/v1/t/{workspaceId}/config/baseline"

Only one baseline is stored per workspace. Saving a new baseline overwrites the previous one.

Checking for drift

1. Go to Settings → Import / Export → Drift
2. Click Check Drift

AlgoBridge compares the current live mappings against the saved baseline and shows a diff:

Via API:

curl -H "Authorization: Bearer sfbs_tok_xxxxxxxxxxxx" \
  "https://your-instance.example.com/api/v1/t/{workspaceId}/config/drift"

Response (drift detected):

{
  "success": true,
  "data": {
    "baseline_id": "bl_01j9...",
    "captured_at": "2026-05-01T08:00:00Z",
    "drifted": true,
    "changes": [
      {
        "mapping_id": "m_01j9...",
        "sf_object": "Contact",
        "type": "field_removed",
        "field": "HomePhone"
      },
      {
        "mapping_id": "m_02j9...",
        "sf_object": "Opportunity",
        "type": "direction_changed",
        "from": "bidirectional",
        "to": "sf_to_pg"
      }
    ]
  }
}

If no drift is detected, drifted is false and changes is an empty array.

Schema drift (Salesforce field changes)

Schema drift is distinct from configuration drift — it refers to changes on the Salesforce side: a field you mapped was renamed or deleted in Salesforce.

AlgoBridge detects schema drift automatically. When a mapped field disappears from Salesforce:

• An alert is shown in the notification center
• The affected mapping is flagged in the Mappings list
• An email is sent to workspace admins

Resolving schema drift requires editing the mapping to remove or replace the missing field. See Alerts & Notifications for the full schema drift workflow.