How to Transfer an ICP from One Region to Another Without Copying Assumptions

Who this guide is for

This guide is for exporters, manufacturers, industrial suppliers, and cross-border GTM teams adapting an existing ICP to another country, province, state, or sales region. It is particularly useful when the team is tempted to translate its current list, swap a country filter, and keep every other assumption unchanged.

Contents

1 Define the portable core and local overlay 2 Crosswalk classifications and account units 3 Rebuild relationship and application evidence 4 Revalidate access, import, delivery, and service 5 Validate the destination universe and account unit 6 Run a regional transfer test 7 Use the transfer worksheet 8 Illustrative example 9 Common mistakes 10 What this does not mean 11 Common questions 12 Sources and methodology

1. Define the portable core and local overlay

Start with two columns. Candidate portable core

• the physical or operational problem;

• product capability and application compatibility;

• conditions under which value is created;

• non-negotiable technical limitations;

• relationship logic that genuinely survives the region change. Local operating overlay

• classifications and universe sources;

• firm, establishment, facility, and parent structure;

• common route to market;

• procurement and qualification conditions;

• import, tax, documentation, and product-access checks;

• delivery, installation, warranty, and service feasibility;

• language and evidence availability;

• exclusions, conflict rules, and review cadence. Label every original criterion retain, translate, replace, or retire. "Retain" requires evidence that the meaning and consequence remain stable. "Translate" means the purpose stays but its local definition or source changes. "Replace" means a different observable is needed. "Retire" means the original condition is irrelevant or harmful in the destination.

2. Crosswalk classifications and account units

NAICS supports North American statistical comparability, but the versions are not identical at every level. The U.S. Census Bureau describes NAICS as the standard used by U.S. federal statistical agencies to classify business establishments. U.S. Census Bureau NAICS Statistics Canada explains that Canada, Mexico, and the United States maintain a common conceptual framework, with national detail and revisions; its introduction also defines the establishment and classification approach. Statistics Canada, NAICS Canada 2022 Introduction Build a crosswalk with:

• origin code, title, version, and scope;

• destination code, title, version, and scope;

• inclusions and exclusions;

• level of commonality;

• unmatched activities;

• implication for the account universe;

• validation owner. Do not map only the numeric code. Read the definitions and index entries, then test named establishments on both sides. The unit may also change. U.S. County Business Patterns defines an establishment as a single physical location and explains multi-unit company treatment and coverage. County Business Patterns methodology If the origin model was built from firms but the destination source counts locations, apparent market depth and account duplication can change without any change in real opportunity.

3. Rebuild relationship and application evidence

Do not assume that the same application is bought through the same relationship. Recheck:

• direct end user versus distributor-led purchase;

• OEM design-in versus aftermarket replacement;

• contractor or integrator specification influence;

• centralized versus facility-level procurement;

• authorized service or channel requirements;

• local inventory expectation;

• private-label or localization requirements. For each relationship type, write who owns inventory, who specifies, who buys, who receives, who installs, who supports, and who carries warranty risk. This does not map the individuals in the buying committee; it establishes the commercial account structure. Application evidence also needs localization. A process may share an industry label while operating under different inputs, climate, duty cycles, standards, installed base, or maintenance models. Use first-party facility pages, product documents, public filings, tenders, authorized-partner directories, and verified interviews. Preserve the facility and observation date.

4. Revalidate access, import, delivery, and service

Create separate gates for: 1 product and application compatibility; 2 lawful and operational market access; 3 delivery and import route; 4 commissioning and serviceability; 5 relationship or channel conflict. For Canada, the Canada Border Services Agency's guide requires importers to identify goods, origin, tariff classification, permits or restrictions, and other import conditions relevant to the product. CBSA Guide to Importing Commercial Goods - Preparing to Import This is an official import-process reference, not a substitute for product-specific legal, tax, customs, or regulatory advice. Public procurement also has local routes. CanadaBuys publishes tender opportunities and links to procurement and contracting information. CanadaBuys Tender Opportunities A tender can establish a dated requirement and buying organization, but it does not prove supplier eligibility, technical compliance, or win probability. For service, calculate a feasible promise from actual locations, partners, parts, hours, language, and escalation. Do not transfer an origin-region service level if the destination lacks the same footprint.

5. Validate the destination universe and account unit

Start with an existing destination-region account universe whose construction, identity resolution, deduplication, and source lineage are already governed. Building that universe belongs in How to Build a Target-Account Universe from Public and Commercial Data (MI-10). This regional-transfer guide validates whether the existing universe can support the transferred ICP; it does not create or expand the candidate population. Before applying origin-region rules, inspect the destination universe contract:

• universe ID, version, owner, and extraction date;

• source owner, table, reference period, and release date;

• geography, classification version, and coverage boundary;

• whether records are firms, enterprises, legal entities, establishments, facilities, or locations;

• employee or size-band definition;

• exclusions, suppression, and confidentiality treatment;

• identity-resolution and parent-child rules;

• duplicate, unresolved, and out-of-scope record counts. Reconcile the records by one declared unit. Show the starting record count, duplicates resolved, records held for identity review, out-of-scope exclusions, and usable destination records. If the origin ICP assumes facilities but the destination universe contains enterprises, stop and require the separately governed universe process to create or verify the facility layer before sampling; do not silently score enterprise fields as facility evidence. Statistics Canada's current Canadian Business Counts table provides location counts with employees by employment-size range, NAICS, census metropolitan area, and census subdivision for its stated reference period. Statistics Canada, Canadian Business Counts The table counts statistical locations, not automatically distinct buying companies. Use it to validate source scope and unit interpretation when relevant, not to add unnamed records inside the transfer exercise. If the destination universe is missing, materially stale, or built on the wrong unit, pause the transfer and return to MI-10. Trade data may provide product-flow context, but it cannot repair an account universe or establish named-account demand.

6. Run a regional transfer test

Use a fresh, bounded sample drawn from the validated destination-region universe and covering:

• multiple destination subregions;

• center and boundary cases;

• origin-region relationship types;

• suspected local relationship alternatives;

• single-site and multi-site organizations;

• easy and difficult evidence environments;

• direct and partner routes. Apply the origin ICP unchanged first as a diagnostic. Then apply the proposed regional overlay. Record which decisions change and why. Evaluate:

• classification match rate;

• identity and facility resolution;

• application evidence coverage;

• relationship reassignment;

• gate pass, fail, and unresolved states;

• direct, partner, wait, and exclude routes;

• researcher agreement;

• incremental research and service cost. Do not combine origin and destination outcomes unless eligibility, definitions, exposure, and observation periods are genuinely comparable.

7. Use the transfer worksheet

Domain Origin assumption Destination evidence Action Owner Application [Claim] [Facility evidence] Retain/Translate/Replac e/Retire [Role] Classification [Code/version] [Code/version/scope] [Action] [Role] Unit [Firm/site] [Local unit] [Action] [Role] Relationship [Route] [Local route evidence] [Action] [Role] Access [Requirements] [Official/local evidence] [Action] [Role] Delivery [Incoterm/import route] [Verified route] [Action] [Role] Service [Promise] [Coverage evidence] [Action] [Role] Exclusions [Rules] [Local risks/conflicts] [Action] [Role] Finish with an explicit decision: reuse with overlay, redesign as a distinct ICP, test through a partner, wait, or do not transfer.

8. Illustrative example

Illustrative example - fictional. A fictional U.S. supplier transfers an end-user process-equipment ICP to Canada. A separately governed Canadian account-universe process has already resolved destination identities and locations. The transfer team validates that universe's source scope and location unit, then draws 48 fictional Canadian locations across four regions and several size bands for its bounded test. Result after local research Locations Confirmed application and relationship fit 30 Confirmed non-fit 10 Application or identity unknown 8 Total 48 Observed confirmed-fit share = 30 / 48 x 100 = 62.5%. This is a diagnostic sample result, not a Canadian market estimate. The 30 confirmed-fit locations are routed again:

• Directly accessible and serviceable: 18 / 30 = 60.0%.

• Partner route required: 8 / 30 = 26.7%.

• Access or service unresolved: 4 / 30 = 13.3%. The original U.S. ICP assumed direct service and treated a location count as if each location were a separate buying company. Canadian research finds that several locations share procurement and that eight fitting sites require a local partner route. The decision is Reuse the technical core with a Canadian regional overlay and retest, not copy the U.S. ICP unchanged. The figures are fictional and do not forecast sales.

9. Common mistakes

• Changing only the country field: every other origin assumption remains hidden.

• Constructing the universe inside the transfer test: sourcing, identity resolution, and deduplication escape the MI-10 governance process.

• Matching codes without scope: national details and classification revisions are ignored.

• Counting locations as companies: universe size and buying motions are overstated.

• Assuming the same route to market: distributor, contractor, or centralized procurement roles differ.

• Treating trade as named-account demand: aggregated flows become false intent.

• Copying service promises: parts, response, language, and partner coverage are unverified.

• Using an origin customer list as validation: selection and historical success are transferred as proof.

• Ignoring unresolved access: a strong fit score overrides import, qualification, or delivery gates.

10. What this does not mean

Regional transfer does not require inventing a completely new ICP for every country. It requires evidence that the portable core remains valid and a documented local overlay for what changes. It is not a substitute for constructing or governing the destination account universe under MI-10. Shared NAICS structure does not make company populations identical. A public tender or import series does not prove account intent. This guide is not customs, tax, regulatory, or legal advice.

11. Common questions

Which ICP fields are most likely to transfer? The underlying application problem, product limits, and value mechanism may transfer when operating conditions are comparable. Relationship, access, service, evidence, and account-structure assumptions require local verification. Can we start with the same scorecard? Use it as a diagnostic, not an approved destination model. Reassess gates, definitions, evidence availability, weights, and thresholds before activation. Is NAICS enough for a U.S.-Canada crosswalk? No. It supports statistical classification, but the team must inspect version, national detail, inclusions, exclusions, and whether the coded establishment has the target application. When should the destination become a separate ICP? When application, relationship, gates, evidence, service model, or commercial action differs enough that a regional overlay no longer preserves one decision logic. How should unknown local requirements be handled? Keep them unresolved, assign research ownership, and use a reversible test or hold. Do not inherit a pass from the origin region.

12. Sources and methodology

Official sources define U.S. and Canadian NAICS, U.S. establishment methodology, Canadian location counts, Canadian public tenders, and Canadian import-process considerations. The portable-core model, destination-universe validation, retain/translate/replace/retire labels, regional overlay, sample method, and routing outcomes are SellersGPT editorial tools. 1 U.S. Census Bureau, North American Industry Classification System. https://www.census.gov/naics/. Accessed August 24, 2026. 2 Statistics Canada, Introduction to NAICS Canada 2022 Version 1.0. https://www.statcan.gc.ca/en/subjects/standard/naics/2022/v1/introduction. Accessed August 24, 2026. 3 U.S. Census Bureau, County Business Patterns Methodology. https://www.census.gov/programs-surveys/cbp/technical-documentation/methodology.html. Accessed August 24, 2026. 4 Statistics Canada, Canadian Business Counts, with Employees, Census Metropolitan Areas and Census Subdivisions, December 2025. https://www150.statcan.gc.ca/n1/en/catalogue/3310109701. Accessed August 24, 2026. 5 Government of Canada, CanadaBuys Tender Opportunities. https://canadabuys.canada.ca/en/tender-opportunities. Accessed August 24, 2026. 6 Canada Border Services Agency, Guide to Importing Commercial Goods into Canada - Preparing to Import. https://www.cbsa-asfc.gc.ca/import/guide-eng.html. Accessed August 24, 2026.