Facebook Pages Migration Guide

Availability

Core Standard Plus Pro Enterprise Flex PyAirbyte

Connector type (beta)

Data replication Agent(learn more)

Support Level

Marketplace

Connector Version

3.0.0 (last updated 2 days ago)

CDK Version

7.9.2

Sync Success Rate

Medium

Usage Rate

High

Data workers used

0.2 per sync (Learn more)

Definition ID

010eb12f-837b-4685-892d-0a39f76a98f5

Upgrading to 3.0.0

This version removes the Meta-deprecated legacy Page fields current_location, genre, network, parking and start_info from the page stream schema. The connector no longer requests them.

This version also stops requesting page.live_videos and removes it from the page stream schema. Meta does not make the /{page-id}/live_videos edge available for New Pages Experience Pages; requesting it returns (#10) To use live-video-api ... and the connector maps that response to a configuration error, causing the entire page stream to fail.

caution

These fields are not requested after upgrading, and Meta no longer serves them for New Pages Experience Pages. If you need the last-known values of current_location, genre, network, parking or start_info, export or snapshot those columns before upgrading and refreshing the schema.

Why this change?

Meta deprecated these fields for New Pages Experience Pages in Graph API v26.0, launched on 2026-07-29, and provides no replacement. Meta states that the deprecation will reach all remaining supported Graph API versions approximately 90 days after launch; the exact date is to be confirmed. The connector's error handler fails hard on Tried accessing nonexisting field, so leaving these fields in the request would fail the entire page stream. If you sync a New Pages Experience Page and stay on 2.x, the page stream will start failing once Meta applies the change to all API versions. See the Meta Graph API v26.0 changelog.

Who is affected?

• page — all five fields are removed from the top-level record, and current_location, genre and network are removed from the nested best_page and parent_page objects.
• page.live_videos — the edge is removed from the page stream.
• post — current_location, genre and network are removed from the nested page objects under sponsor_tags[].data[]. parking and start_info were never present there.
• page_insights and post_insights are unaffected; no action is required for them.

No specification, configuration, or state changes are required.

Migration steps

1. Upgrade the connector to version 3.0.0.
2. Refresh the source schema for the page and post streams.
3. Update downstream models or SQL that reference any of the following:
   • page.current_location, page.genre, page.network, page.parking, page.start_info
   • page.live_videos
   • page.best_page.current_location, page.best_page.genre, page.best_page.network
   • page.parent_page.current_location, page.parent_page.genre, page.parent_page.network
   • post.sponsor_tags.data[].current_location, post.sponsor_tags.data[].genre, post.sponsor_tags.data[].network

Clearing the page stream is not required.

Upgrading to 2.0.0

Version v2.0.0 updates the API version from v23 to v24. Deprecated fields have been removed and new fields have been added for the streams Post, Post Insights and Page Insights.

Deprecated fields API docs.

Post Stream - this version declares changes to this stream's schema, removing deprecated fields that are no longer available. Refresh stream schema and clear the stream data to continue using this stream. Please, follow Migration Steps below. Post Insight Stream and Page Insights Stream - this version removes deprecated metrics which are no longer available in the records. The Schema is not changed so refreshing the schema is not needed. It is only recommended that you Clear affected streams if you would like to have all data in one consistent format. Please, follow Migration Steps below for Clearing streams. Otherwise, no action is needed for these streams.

Post Stream Metrics:

Added:

• allowed_advertising_objects
• attachments
• full_picture

Removed:

• event
• expanded_height
• expanded_width
• height
• is_inline_created
• promotion_status
• target
• timeline_visibility
• via
• width
• comments
• dynamic_posts
• likes
• reactions
• sharedposts

Post Insights Stream Metrics:

Added:

• post_media_view

Removed:

• post_impressions
• post_impressions_paid
• post_impressions_fan
• post_impressions_fan_paid
• post_impressions_fan_paid_unique
• post_impressions_organic
• post_impressions_viral
• post_impressions_nonviral
• post_impressions_by_story_type
• post_impressions_by_story_type_unique
• post_engaged_users
• post_negative_feedback
• post_negative_feedback_unique
• post_negative_feedback_by_type
• post_negative_feedback_by_type_unique
• post_engaged_fan
• post_clicks_unique
• post_clicks_by_type_unique

Page Insights Stream Metrics:

Added:

• page_media_view

Removed:

• page_tab_views_login_top_unique
• page_tab_views_login_top
• page_tab_views_logout_top
• page_cta_clicks_logged_in_total
• page_cta_clicks_logged_in_unique
• page_cta_clicks_by_site_logged_in_unique
• page_cta_clicks_by_age_gender_logged_in_unique
• page_cta_clicks_logged_in_by_country_unique
• page_cta_clicks_logged_in_by_city_unique
• page_call_phone_clicks_logged_in_unique
• page_call_phone_clicks_by_age_gender_logged_in_unique
• page_call_phone_clicks_logged_in_by_country_unique
• page_call_phone_clicks_logged_in_by_city_unique
• page_call_phone_clicks_by_site_logged_in_unique
• page_get_directions_clicks_logged_in_unique
• page_get_directions_clicks_by_age_gender_logged_in_unique
• page_get_directions_clicks_logged_in_by_country_unique
• page_get_directions_clicks_logged_in_by_city_unique
• page_get_directions_clicks_by_site_logged_in_unique
• page_website_clicks_logged_in_unique
• page_website_clicks_by_age_gender_logged_in_unique
• page_website_clicks_logged_in_by_country_unique
• page_website_clicks_logged_in_by_city_unique
• page_website_clicks_by_site_logged_in_unique
• page_engaged_users
• page_consumptions
• page_consumptions_unique
• page_consumptions_by_consumption_type
• page_consumptions_by_consumption_type_unique
• page_places_checkin_total
• page_places_checkin_total_unique
• page_places_checkin_mobile
• page_places_checkin_mobile_unique
• page_places_checkins_by_age_gender
• page_places_checkins_by_locale
• page_places_checkins_by_country
• page_negative_feedback
• page_negative_feedback_unique
• page_negative_feedback_by_type
• page_negative_feedback_by_type_unique
• page_positive_feedback_by_type
• page_positive_feedback_by_type_unique
• page_fans_online
• page_fans_online_per_day
• page_impressions
• page_impressions_paid
• page_impressions_organic_v2
• page_impressions_organic_unique_v2
• page_impressions_viral
• page_impressions_nonviral
• page_impressions_by_story_type
• page_impressions_by_story_type_unique
• page_impressions_by_city_unique
• page_impressions_by_country_unique
• page_impressions_by_locale_unique
• page_impressions_by_age_gender_unique
• page_impressions_frequency_distribution
• page_impressions_viral_frequency_distribution

Migration Steps

Clearing data for Post Stream

Clearing your data is required for the affected streams to continue syncing successfully. To clear your data for the affected streams, follow the steps below:

1. Select Connections in the main navbar and select the connection(s) affected by the update.
2. Select the Schema tab.
   1. Select Refresh source schema to bring in any schema changes. Any detected schema changes will be listed for your review.
   2. Select OK to approve changes.
3. Select Save changes at the bottom of the page.
   1. Ensure the Clear affected streams option is checked to ensure your streams continue syncing successfully with the new schema.
4. Select Save connection.

This will clear the data in your destination for the subset of streams with schema changes. After the clear succeeds, trigger a sync by clicking Sync Now. For more information on clearing your data in Airbyte, see this page.

Clearing data for Post Insight and Page Insights Streams

To clear data for a single stream, navigate to a Connection's status page, click the three grey dots next to any stream, and select "Clear data". This will clear the data for just that stream. You will then need to sync the connection again in order to reload data for that stream.

Upgrading to 1.0.0

note

This change is only breaking if you are syncing stream Page.

This version brings an updated schema for the v19.0 API version of the Page stream. The messenger_ads_default_page_welcome_message field has been deleted, and call_to_actions, posts, published_posts, ratings, tabs and tagged fields have been added.

Users should:

• Refresh the source schema for the Page stream.
• Reset the stream after upgrading to ensure uninterrupted syncs.

Refresh affected schemas and reset data

1. Select Connections in the main nav bar.
   1. Select the connection affected by the update.
2. Select the Replication tab.
   1. Select Refresh source schema.
   2. Select OK.

note

Any detected schema changes will be listed for your review.

3. Select Save changes at the bottom of the page.
   1. Ensure the Reset affected streams option is checked.

note

Depending on destination type you may not be prompted to reset your data.

4. Select Save connection.

note

This will reset the data in your destination and initiate a fresh sync.

For more information on resetting your data in Airbyte, see this page

Connector upgrade guide

Review the following information to prepare for and execute your upgrade.

Review the changelog

Before updating a connector, review the changelog to understand the changes and their potential impact on your existing connections. Find the changelog for any connector by navigating to the bottom of the documentation for that connector. Major version releases also include a migration guide.

Plan for major updates

Major updates may require you to adjust connection settings or even make changes to your data pipelines. Allocate enough time and resources for this. Use the migration guide to ensure your transition process goes smoothly.

Airbyte provides tooling that guarantees safe connector version bumps and enforces automated version bumps for minor and patch updates. You always need to manually update for major version bumps.

Self-managed plans: pin a specific version if you can't update

If you're unable to upgrade to the new version of a connector, you can pin that connector to a specific version.

1. In the navigation bar:

   • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

   • If you're on any other plan, click Workspace settings > Sources/Destinations.

2. Edit the entry for the connector you want to pin.

3. Set the Default Version to the version you want to use.

Self-managed plans: update the local connector image

If you self-manage Airbyte, you must manually update the connector image in your local registry before proceeding with the migration. Follow the steps below.

1. In the navigation bar:

   • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

   • If you're on any other plan, click Workspace settings > Sources/Destinations.

2. Find the connector you want to update in the list of connectors.

   note

   Airbyte lists two versions, the current in-use version and the latest version available.

3. Click Change to update your OSS version to the latest available version.

Update the connector version

Update each instance of the connector separately. If you have multiple instances of a connector, updating one doesn't affect the others.

1. In the navigation bar:

   • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

   • If you're on any other plan, click Workspace settings > Sources/Destinations.

2. Select the instance of the connector you wish to upgrade.

3. Select Upgrade.

4. Follow the prompt to confirm you are ready to upgrade to the new version.

Clear data from affected streams

After upgrading a connector with a breaking change, you must refresh affected schemas and clear your data.

1. In the nav bar, click Connections.

2. Find the connection affected by the upgrade.

3. Click the Schema tab.

4. Click Refresh source schema (looks like ). When Airbyte finishes, it shows you any detected schema changes.

5. Click OK.

6. Click Save changes

7. Clear the data for the streams affected by this upgrade.

Once the clear is complete, you can begin syncing your data again as usual.