This guide is useful if you want to migrate your Salesforce source from Segment to RudderStack.

Schema Comparison

In this guide, we compare the schemas of the opportunity table synced by RudderStack and Segment.

RudderStack ColumnsSegment Columns
idid
current_generators_c-
probabilityprobability
context_request_ip-
is_deletedis_deleted
close_dateclose_date
attributes_url-
last_modified_by_idlast_modified_by_id
context_sources_job_id-
context_sources_task_id-
channel-
namename
last_modified_datelast_modified_date
forecast_category_nameforecast_category_name
has_opportunity_line_itemhas_opportunity_line_item
system_modstampsystem_modstamp
forecast_categoryforecast_category
tracking_number_c-
attributes_type-
is_wonis_won
lead_sourcelead_source
event_text-
timestamp-
sent_at-
expected_revenue-
amountamount
created_by_idcreated_by_id
original_timestamp-
owner_idowner_id
fiscal_yearfiscal_year
order_number_c-
is_private-
has_overdue_taskhas_overdue_task
loaded_atloaded_at
context_ip-
descriptiondescription
event-
has_open_activityhas_open_activity
fiscalfiscal
user_id-
stage_namestage_name
main_competitors_c-
context_sources_job_run_id-
fiscal_quarterfiscal_quarter
typetype
account_idaccount_id
created_datecreated_date
received_atreceived_at
uuid_tsuuid_ts
delivery_installation_status_c-
context_sources_task_run_id-
is_closedis_closed

A blank value indicates that the column was not sent to the platform.

Since the column names are identical for the Salesforce source in both RudderStack and Segment, the migration should not require any additional coding or modification to the tables.

Here's a high-level summary of the number of columns synced to RudderStack, as compared to Segment:

Columns synced to RudderStackColumns synced to SegmentNumber of common columnsColumns missing in RudderStackColumns missing in Segment
523030022

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.