diff --git a/common.proto b/common.proto
index 2f09d03..b421a91 100644
--- a/common.proto
+++ b/common.proto
@@ -1,8 +1,8 @@
 syntax = "proto3";
 option optimize_for = SPEED;
 option java_multiple_files = true;
-option go_package = "fivetran.com/fivetran_sdk";
-package fivetran_sdk;
+option go_package = "fivetran.com/partner_sdk";
+package partner_sdk;
 
 import "google/protobuf/timestamp.proto";
 
diff --git a/connector_sdk.proto b/connector_sdk.proto
index 4d906ee..1aab7ac 100644
--- a/connector_sdk.proto
+++ b/connector_sdk.proto
@@ -1,8 +1,8 @@
 syntax = "proto3";
 option optimize_for = SPEED;
 option java_multiple_files = true;
-option go_package = "fivetran.com/fivetran_sdk";
-package fivetran_sdk;
+option go_package = "fivetran.com/partner_sdk";
+package partner_sdk;
 
 import "common.proto";
 
diff --git a/destination_sdk.proto b/destination_sdk.proto
index 8c5635b..1240554 100644
--- a/destination_sdk.proto
+++ b/destination_sdk.proto
@@ -1,8 +1,8 @@
 syntax = "proto3";
 option optimize_for = SPEED;
 option java_multiple_files = true;
-option go_package = "fivetran.com/fivetran_sdk";
-package fivetran_sdk;
+option go_package = "fivetran.com/partner_sdk";
+package partner_sdk;
 
 import "google/protobuf/timestamp.proto";
 import "common.proto";
diff --git a/development-guide.md b/development-guide.md
index 86ad9db..c089588 100644
--- a/development-guide.md
+++ b/development-guide.md
@@ -121,7 +121,7 @@ Do not assume order of columns in the batch files. Always read the CSV file head
     - `unmodified_string` value is used to indicate columns in `update_files` where the values did not change.
 
 ### Examples of Data Types
-Examples of each [DataType](https://github.com/fivetran/fivetran_sdk/blob/main/common.proto#L73C6-L73C14) as they would appear in CSV batch files are as follows:
+Examples of each [DataType](https://github.com/fivetran/partner_sdk/blob/main/common.proto#L73C6-L73C14) as they would appear in CSV batch files are as follows:
 - UNSPECIFIED: This data type will never appear in batch files
 - BOOLEAN: "true", "false"
 - SHORT: -32768 .. 32767
diff --git a/examples/connector/golang/go.mod b/examples/connector/golang/go.mod
index 2465455..508aed7 100644
--- a/examples/connector/golang/go.mod
+++ b/examples/connector/golang/go.mod
@@ -1,4 +1,4 @@
-module fivetran.com/fivetran_sdk
+module fivetran.com/partner_sdk
 
 go 1.21
 
diff --git a/examples/connector/golang/golang_connector/main.go b/examples/connector/golang/golang_connector/main.go
index e26eb6d..36634da 100644
--- a/examples/connector/golang/golang_connector/main.go
+++ b/examples/connector/golang/golang_connector/main.go
@@ -9,7 +9,7 @@ import (
 	"net"
 	"strconv"
 
-	pb "fivetran.com/fivetran_sdk/proto"
+	pb "fivetran.com/partner_sdk/proto"
 	"google.golang.org/grpc"
 )
 
diff --git a/examples/connector/java/src/main/java/connector/ConnectorServiceImpl.java b/examples/connector/java/src/main/java/connector/ConnectorServiceImpl.java
index f822398..e27b421 100644
--- a/examples/connector/java/src/main/java/connector/ConnectorServiceImpl.java
+++ b/examples/connector/java/src/main/java/connector/ConnectorServiceImpl.java
@@ -2,8 +2,8 @@
 
 import com.fasterxml.jackson.core.JsonProcessingException;
 import com.fasterxml.jackson.databind.ObjectMapper;
-import fivetran_sdk.*;
-import fivetran_sdk.Record;
+import partner_sdk.*;
+import partner_sdk.Record;
 import io.grpc.stub.StreamObserver;
 
 import java.util.*;
diff --git a/examples/destination/java/src/main/java/destination/DestinationServiceImpl.java b/examples/destination/java/src/main/java/destination/DestinationServiceImpl.java
index 738e748..f00a802 100644
--- a/examples/destination/java/src/main/java/destination/DestinationServiceImpl.java
+++ b/examples/destination/java/src/main/java/destination/DestinationServiceImpl.java
@@ -1,6 +1,6 @@
 package destination;
 
-import fivetran_sdk.*;
+import partner_sdk.*;
 import io.grpc.stub.StreamObserver;
 
 import java.util.Arrays;
diff --git a/tools/connector-tester/README.md b/tools/connector-tester/README.md
index d4fb2da..d7e11f7 100644
--- a/tools/connector-tester/README.md
+++ b/tools/connector-tester/README.md
@@ -24,7 +24,7 @@ docker start -i <container-id>
 
 ## CLI Arguments
 
-The tester supports the following optional CLI arguments to alter its default behavior. You can append these options to the end of the docker run command provided in step 2 of [How To Run](https://github.com/fivetran/fivetran_sdk/blob/main/tools/connector-tester/README.md#how-to-run) section above.
+The tester supports the following optional CLI arguments to alter its default behavior. You can append these options to the end of the docker run command provided in step 2 of [How To Run](https://github.com/fivetran/partner_sdk/blob/main/tools/connector-tester/README.md#how-to-run) section above.
 
 #### --port
 This option tells the tester to use a different port than the default 50051.
diff --git a/tools/destination-tester/README.md b/tools/destination-tester/README.md
index 62d5302..3e1aa94 100644
--- a/tools/destination-tester/README.md
+++ b/tools/destination-tester/README.md
@@ -21,7 +21,7 @@ docker start -i <container-id>
 
 ## Input Files
 
-Destination tester simulates operations from a source by reading input files from the local data folder. Each input file represents a batch of operations, encoded in JSON format. Data types in [common.proto](https://github.com/fivetran/fivetran_sdk/blob/main/common.proto#L73) file can be used as column data types.
+Destination tester simulates operations from a source by reading input files from the local data folder. Each input file represents a batch of operations, encoded in JSON format. Data types in [common.proto](https://github.com/fivetran/partner_sdk/blob/main/common.proto#L73) file can be used as column data types.
 
 ### List of Operations
 
@@ -143,7 +143,7 @@ Here is an example input file named `input_1.json`:
 
 ## CLI Arguments
 
-The tester supports the following optional CLI arguments to alter its default behavior. You can append these options to the end of the `docker run` command provided in step 2 of [How To Run](https://github.com/fivetran/fivetran_sdk/tree/main/tools/destination-tester#how-to-run) section above.
+The tester supports the following optional CLI arguments to alter its default behavior. You can append these options to the end of the `docker run` command provided in step 2 of [How To Run](https://github.com/fivetran/partner_sdk/tree/main/tools/destination-tester#how-to-run) section above.
 
 #### --port
 This option tells the tester to use a different port than the default 50052.