Sync WordPress Staff Profiles Without Losing Local Edits

A staff feed can save editors time, but it needs clear rules about what it may change. The central system might own a biography and job title while the destination site owns publication status and local notes. Without those rules, a scheduled sync can overwrite useful edits or remove a profile that still needs to exist. In a staff synchronization workflow, I added previews, reviewed matching, and photo reuse before relying on scheduling. The aim was straightforward: an editor should be able to see what the next run will do and understand why each profile will change.

Assign an owner to each profile field

The central source knew who belonged to each brand and supplied shared profile fields. The destination site still owned local publication state, selected overrides, and the decision to expose a profile. Treating the feed as total authority would have overwritten editorial work; treating it as optional reference would have allowed stale staff information to persist.

I documented ownership field by field. The sync could update feed-owned values while preserving local fields outside the agreed update rules. This made disagreements visible instead of resolving them by whichever process wrote last.

Preview creates, updates, and removals

Before any write, the operator can see proposed creates, updates, unchanged records, skipped rows, and possible removals. The preview needs to predict the actual changes. It uses the same matching and value-cleanup rules as the update, so it is a rehearsal of the real decision.

I learned to include reasons, not only counts. “Five skipped” is weak. “Five skipped because their required photos are incomplete” tells the operator what can be fixed and confirms that the system did not silently discard them.

Enrollment made automation intentional. Existing local profiles were not automatically handed to the feed. I added a manual enrollment workflow that links a reviewed local record to its central identity. Feed-only staff could also be created through a controlled action.

This step prevented name similarity from becoming authority. Slugs and stable source identifiers were prioritized, compatibility values were normalized, and uncertain matches stayed in review rather than being forced.

Reuse photos when the source is unchanged

Downloading a profile photo on every sync would create duplicate attachments and unnecessary processing. I recorded the remote source identity and reused an existing attachment when the image had not changed. A repeat sync therefore produced the same media relationship instead of another file.

I also kept image failure separate from profile identity. A temporary media problem should not make the system invent a new person or lose the durable link it already knows.

Responsive actions matter during long operations. Once the workflow grew beyond a tiny feed, a single opaque request was not enough. Review and manual sync actions needed clear progress, bounded work, and stable results if the browser waited or retried.

My acceptance checklist became: preview equals execution logic; reruns are safe; remote identity persists; images deduplicate; local-only fields survive; removals require an explicit policy; and every outcome is explainable to an editor.

Keep publication and removal decisions clear

A fast sync that occasionally publishes the wrong person or removes a valid profile is not efficient. It shifts cost to support, editorial review, and reputation. A controlled workflow may add one approval step, but it removes hours of detective work after a silent mistake.

Scheduling can use these same rules. A feed response should update only the fields and profiles that the sync has been configured to manage.

Removal was the most sensitive operation. Creating and updating profiles received most of the early attention, but removal had the larger consequence. A person missing from today’s feed might have left the organization, been temporarily excluded by a source error, or moved between brand assignments. Automatically trashing the local profile would turn a transient feed problem into a public content incident.

I separated “not present,” “not eligible for this site,” and “explicitly inactive” where the source provided enough information, and surfaced proposed removals in review. I also preserved attribution needs: an author who leaves may still need to remain available as the historical byline on published content even when their directory profile is no longer promoted. That led to a broader rule I now reuse: a profile’s sync status should be separate from the identity used for historical bylines. Removal policy must say what disappears from listings, what remains resolvable, what happens to authored content, and who approves the transition.

Auditability completed the workflow. Each run records when it occurred, which source it used, what actions were proposed, and what the operator approved. I avoid storing unnecessary personal data in logs, but I keep enough identifiers and outcome codes to reconstruct why a public profile changed. That history is especially valuable when source teams and site editors are different people.

Prepare the workflow before adding a schedule

Before scheduling a staff sync, agree on field ownership, matching rules, and removal policy. Test the preview against the actual update results, then rerun the same feed to check for duplicate profiles and photos. Include local edits, missing images, ambiguous matches, and staff absent from one feed response. Keep uncertain changes in review. Scheduling becomes useful once the people maintaining the directory can explain the proposed changes and recover from a failed run.

Photo by Walls.io on Pexels.