Skip to content
CHHS → Find Your Energy · Migration review

ACF & shared-content crosswalk

Suggested transfer rules for the field groups and reusable content named in the source guides.

Move content into the destination’s data model

Legacy slabs and sidebar repeaters become block content or reusable compositions. Header and site-wide options still use ACF, but the destination’s group names, keys and field structures differ. These rows cover every group named in the source guide, with shared sidebar/table options split to make their reuse rules explicit.

Source: CHHS field-group inventory and RDC additions. The supplied guide lists groups, not complete field schemas or conditional logic; treat these as transfer rules to validate against source data and destination editor fields.

Legacy group / shared contentSuggested destinationTransfer ruleGap / validation
Navigation SettingsACF: Page Options (options page) · Breadcrumbsshow_breadcrumbs → breadcrumbs in Page Options.Site-wide default versus legacy page/navigation settings: preserve per-page exceptions only after checking destination support.
Sidebar Nav SettingsACF: Theme: Page Header · All Other WordPress Core BlocksCurated links → user_action_box=nav, navigation_heading, navigation_menu, assign_nav_to_children.Display/reset-to-current-page and automatic tree generation have no documented one-to-one equivalent. A maintained tree component is required if retained.
Page Header / Reusable SlabsACF: Theme: Page Header · ACF: Theme: Featured Image CaptionImage → Featured Image; body → page_header_description; button/secondary link → buttons[].link; header style → basic/primary/secondary; title → page title/highlight_text_lines.Superhead/subhead require editorial mapping; a page title can become kicker. Texture/overlay values do not transfer. Reusable header references must be resolved or deliberately reimplemented.
Homepage HeaderPage Header: Primary (hero) · ACF: Theme: Page Header · Pattern: Highlight List with TextHeader text/image → Primary header + Theme: Page Header; Header Facts → Highlight List with Text or a composed stats pattern.No separate homepage Header Facts field is listed. Put facts in content blocks; ensure the hero remains the sole logical page heading.
Flexible Landing Page ContentPattern: Media & Text · Call to Action (default / no style) · SOURCE Stories (default) · Trumba Eventsflex_slabs → ordered page-content blocks/patterns. Use the component catalog for each layout and variant.Legacy ACF flexible-content rows are not consumed by FYE blocks. Convert content, not just group registration.
Standard Page ContentHeading, Paragraph, List, Link, Quote and Table Defaults · Columns: Divider variants · Groupflex_slabs → core/Stalwart blocks; sidebar Contact/Teasers → composed contact Group and one-column CTA cards.A sidebar/page-tree layout needs its own reusable page composition or template; default FYE page flow does not establish parity.
Academic Unit ContentPage Header: Secondary (side by side) · Columns: Divider variants · SOURCE Stories (default)flex_slabs → main flow; sidebar → optional column; flex_slabs_wide → subsequent wide/full groups.Preserve separate content-region ordering and responsive sequence; no matching Academic Unit template is demonstrated.
Filtered Directory ListingContent Query (default)Directory options → Content Query attributes only after people become a registered local post type, with taxonomies/filters and person detail templates.Content Query uses block attributes, not a corresponding ACF group. External directory widgets require a maintained integration instead.
Footer Content (options)ACF: Site Layout (options page) · Site Footer · ACF: Social Media (options page)Footer menus → footer_menu_left/center/right/extra; social links → social_media_links platform/account_url; configure network inheritance.Address/contact name/link are not in the listed FYE footer options; preserve them explicitly in a contact area or footer extension.
Site Title Link (options)Site Header · ACF: Site Layout (options page)Recreate site identity and destination link through the header/site settings; enable network home link when appropriate.The guide does not document a free-form Site Title Link equivalent. Check whether the legacy custom title URL can be retained before assuming automatic mapping.
Sitewide Alerts (options)ACF: Site Layout (options page) · Site AlertHeadline + body → alert_content; set alert_enabled, alert_push_to_network, alert_scope, alert_cookie_duration, alert_expiry.Icon and severity need editorial conversion or custom support. Test dismissal and network/local precedence; legacy alert exists despite destination guide’s GAP label.
Reusable Sidebar BlocksGroup · Call to Action (default / no style) · ACF: Block: Call to ActionResolve each shared Contact/Teaser reference and create a synced block pattern when updates should propagate across pages.A duplicated unsynced pattern loses shared-update behavior. Audit site/network reuse, ownership and editing permissions.
Table Slab (shared options)TableConvert the table data to core/table and store it as a synced pattern when multiple pages share it.Preserve header/footer rows, caption and first-column header semantics; replace every reference to the legacy reusable table.
Menu Fields / Menu Item FieldsSite Header · Site Footer · ACF: Social Media (options page)Map navigation to destination menu locations and footer social items to the Social Media repeater.Menu icons/extras do not have a documented field equivalent. Check each use; do not import legacy field metadata and expect it to render.
RDC Home Page Header / ContentPage Header: Primary (hero) · Pattern: Call to Action Cover · QuoteImage hero → Primary; flex_slabs → content blocks including Quote composition. Video hero → custom Cover composition with title/body/actions.RDC-only: homepage_header video file/poster and texture options are not listed in FYE ACF. Preserve video workflow separately and avoid duplicate theme/content heroes.

Destination fields to configure deliberately

Before switching themes, preserve a source-content export, resolve shared references and attachment IDs per site, then verify each converted page’s headings, links, captions, embeds and shared-update behavior in a test installation.