Are electronic signatures valid?

Yes. Electronic signatures are generally legally valid under the ESIGN Act (15 U.S.C. ch. 96, 2000) and state UETA laws when intent, consent, attribution, and record retention are satisfied.

When is notarization required?

Not all portability requests need notarization; certain transfers or state-specific filings may require a notary or witnesses. Verify with the receiving provider or state law before submitting.

Who can sign for the business?

An officer listed in corporate records, an authorized manager, or someone with a power of attorney may sign. Attach board resolutions or POAs when authority is not evident.

How do I correct a submitted form?

Contact the receiving provider immediately, submit an amended form with clear reference to the original, and retain both versions for audit and dispute resolution.

What evidence should accompany the form?

Provide a recent account statement, proof of business registration, government ID for the signer, and any provider-specific references requested during validation.

Electronic vs. digital signatures?

Electronic signatures are a broad legal category; digital signatures use cryptographic PKI technology. Both can be valid, but higher-risk transfers may require stronger signer authentication.

Electronic Signature
Templates
Miscellaneous
Business Portability Form

Business Portability Form

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

Business Portability Form

This Business Portability Form (the Agreement) documents the terms by which the business operations, assets, and related data described below will be ported from the Assignor to the Assignee pursuant to the terms set forth.

Parties

Assignor (Porting Business): Assignor Business Address: Assignee (Receiving Business): Assignee Business Address:

WHEREAS

WHEREAS, Assignor operates certain business operations, customer accounts, records, proprietary configurations, and related assets described below (collectively, Ported Assets); and

WHEREAS, Assignee desires to receive the Ported Assets and to assume operation of certain functions in accordance with the terms and conditions of this Agreement; and

WHEREAS, the Parties intend that the transfer shall be governed by the mutually agreed obligations, payment terms, confidentiality protections, and regulatory compliance provisions set forth herein.

Scope of Portability

The Assignor shall port the following Ported Assets to the Assignee as of the Effective Port Date specified below. The parties acknowledge that the scope below is intended to be exhaustive for the purposes of transfer and assumption of operational responsibilities.

Effective Port Date: Detailed Scope (describe systems, accounts, customer data, intellectual property, licenses, equipment, and other assets to be ported): Excluded Items (if any):

The Assignor represents that it has the authority to port the Ported Assets and that any customer data included in the transfer either: (a) is permitted to be transferred under applicable law and contract; or (b) will be transferred only after obtaining required consents. Assignee shall be responsible for post-transfer compliance with applicable privacy, consumer protection, and data security obligations.

Payment Terms

As consideration for the Ported Assets and the Assignor's transfer obligations, Assignee shall pay Assignor the amounts and according to the schedule set forth below.

Total Consideration (USD): Deposit or Initial Payment: Payment Schedule / Milestones: Late Payment Fee (annualized rate or flat fee):

Unless otherwise agreed in writing, invoices not paid within thirty (30) days of issuance shall accrue the late payment fee described above and the prevailing party shall be entitled to recover collection costs, including reasonable attorneys' fees.

Term and Termination

This Agreement becomes effective on the Effective Port Date specified above and shall continue until the completion of the transfer obligations and any post-transfer transition obligations described herein, or until earlier termination as provided below.

Anticipated Completion Date: Termination Notice Period (days): Termination for Cause (describe material breaches enabling termination):

Upon termination for material breach, the non-breaching party may pursue all remedies available at law or equity, and shall be entitled to retain or recover any amounts due for services rendered and costs incurred through the effective date of termination.

Confidentiality

Each Party shall maintain in strict confidence all non-public information disclosed by the other Party in connection with the portability, including, without limitation, customer lists, account data, pricing, processes, software configurations, and trade secrets (Confidential Information). Confidential Information shall not include information that: (a) is or becomes public through no fault of the recipient; (b) is rightfully received from a third party without restriction; or (c) is independently developed without use of the disclosing Party's Confidential Information.

The recipient shall use Confidential Information solely for the purposes of performing under this Agreement, shall limit access to personnel who have a need to know, and shall apply reasonable administrative, physical and technical safeguards to protect such Confidential Information. Upon termination or request, recipient shall, at the discloser's option, return or destroy Confidential Information and certify such return or destruction in writing.

Representations and Warranties

Each Party represents and warrants that it has full power and authority to enter into this Agreement and to perform its obligations hereunder. Assignor further represents that, to the best of its knowledge, transfer of the Ported Assets will not violate any material contract, law, or third-party right, and that all material taxes, fees, and liens related to the Ported Assets have been disclosed.

Indemnification

Each Party shall indemnify, defend and hold harmless the other Party from and against any and all claims, liabilities, losses, damages, costs and expenses (including reasonable attorneys' fees) arising out of the indemnifying Party's breach of this Agreement, willful misconduct, or failure to comply with applicable laws in connection with the Ported Assets.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the state specified below, without regard to conflict of law principles.

Governing State:

Entire Agreement; Amendment

This Agreement constitutes the entire agreement between the Parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings, negotiations and discussions, whether oral or written. Any amendment or modification to this Agreement must be in writing and signed by authorized representatives of both Parties.

Acknowledgments and Certifications

The undersigned certify that they are authorized to execute this Agreement on behalf of the respective Parties and that the information provided in this form is true, complete and accurate to the best of their knowledge. Each Party acknowledges receipt of adequate consideration and understands the obligations assumed herein.

Assignor Printed Name:

By:

Date:

Assignee Printed Name:

By:

Date:

What the Business Portability Form Is and when it’s used

A Business Portability Form documents an authorized request to transfer business identifiers, accounts, or services from one provider to another. Common uses include transferring telecom numbers, moving vendor accounts, migrating merchant or payment relationships, or assigning service contracts when ownership changes. The form identifies the business, lists account or service identifiers, names an authorized representative, and records explicit consent to the transfer. When completed correctly it establishes permission, routing instructions, and verification data that providers use to avoid service interruptions and maintain historical continuity of business records.

Why a clear portability form matters for continuity and compliance

A properly completed Business Portability Form reduces service downtime, clarifies authorization, and creates an auditable record of consent. It helps providers validate requests quickly, supports dispute resolution, and — when executed electronically — can meet U.S. e-signature law standards such as the ESIGN Act (15 U.S.C. ch. 96, 2000) and applicable UETA provisions.

Typical organizations and people who complete this form

The form is used by companies of all sizes and by their service providers during account or identifier transfers.

Small businesses and sole proprietors initiating transfers for phone numbers, payment processors, or supplier accounts to avoid service gaps.
Mid-market and enterprise IT or procurement teams coordinating bulk migrations, vendor replacements, or cloud service consolidations.
Carriers, banks, and SaaS vendors accepting portability requests from authorized representatives and validating identity and account ownership.

Each signer should match the authority named on the form and provide any supporting identity documents requested by the receiving provider.

Essential parts of a professional Business Portability Form

A complete form combines clear authorization language, precise identifiers, signer authority, verification steps, and retention instructions to make the request actionable and defensible.

Business identification

Full legal business name, DBA if applicable, and federal tax ID or EIN so recipients can match corporate records and avoid cross-account errors.

Account identifiers

Exact account numbers, phone numbers, merchant IDs, or other service IDs being ported; imprecise identifiers cause rejections or delays.

Authorized representative

Name, title, contact details, and a statement of authority (board resolution or power of attorney if required) that proves the signer can bind the business.

Consent and scope

Clear language describing what is being transferred, acceptance by the new provider, and any limitations or conditions on the transfer.

Verification and attachments

IDs, recent bills, account statements, or provider-specific reference numbers used to validate ownership and speed processing.

Retention and audit trail

A clause stating how long records will be retained and confirming that the executed form may be reproduced for audit or dispute resolution.

Step-by-step: how to complete and submit a portability request

Follow this sequence to prepare a complete, verifiable request that providers can process without unnecessary back-and-forth.

01

Gather IDs: Collect EIN, account statements, and government IDs.
02

Confirm authority: Obtain board resolution or POA if signer lacks officer title.
03

Complete form: Fill fields exactly and attach evidence.
04

Submit and track: Send to both old and new providers; retain receipts.

How a typical electronic portability workflow is configured

Standard e-submission workflows collect required fields, enforce signer order, and capture an audit trail for compliance.

Field	Configuration
Required fields	Make business name, EIN, account ID, signer, and effective date mandatory.
Signer order	Set receiving provider or legal reviewer as final signer in sequence.
Authentication	Use email plus SMS or ID check for higher-risk transfers.
Audit trail	Enable timestamp, IP, and certificate capture for each signing event.

Typical processing flow after you submit the form

Understanding the post-submission steps helps you anticipate requests for further verification or expected confirmations.

Receipt confirmation: Provider issues acknowledgement and tracking reference.
Validation: Recipient verifies account ownership and documents.
Acceptance: Receiving provider confirms transfer window and service cutover.
Completion: Service moves and audit trail is finalized.

How to support electronic completion and eSubmission

Choose a platform that supports required file formats, signer authentication, and preserves a full audit trail for legal defensibility.

File formats: PDF, DOCX, or fillable PDF
Authentication: Email link, SMS code, or ID verification
Integrations: CRM, cloud storage, and ERP

Typical timing and processing expectations

Processing times vary by industry and provider. Plan for confirmation windows, validation checks, and any contractual notice periods before the effective date.

Acknowledgement window:

Providers usually confirm receipt within 24–72 hours.

Validation period:

Verification can take 1–10 business days depending on complexity.

Effective timing:

Effective date may require coordinated cutover windows.

Provider notice:

Some contracts require 30 days’ advance notice for changes.

Document retention:

Keep confirmation and signed form per retention rules.

Common mistakes that cause delays or rejections

Incorrect account or phone digits submitted, causing provider to reject or route the request to the wrong account and delay processing.
Signer listed without documented authority, such as lack of a board resolution or power of attorney when required by the receiving provider.
Missing or unclear effective date that disagrees with provider scheduling or billing cycles, leading to prorate disputes or unintended charges.
Submitting scanned, low-resolution ID or bill copies that fail provider identity-proofing checks and trigger manual verification steps.

Risks and potential consequences of errors on portability requests

Service interruption: Missing or incorrect data can cause temporary loss of service.

Billing disputes: Incorrect effective dates may create prorate or double-billing issues.

Contract penalties: Early termination or notice failures may trigger fees.

Regulatory exposure: Improper transfers of regulated identifiers may attract scrutiny.

Data mismatch: Mismatched legal names risk refusal to port accounts.

Reputational harm: Repeated errors reduce partner trust and complicate future transfers.

Representative eSignature vendor comparison for portability workflows

Compare starting price and key feature availability across vendors commonly used for business portability forms; signNow is listed first per comparison standards.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial, no card	Varies by region	Varies by plan	Limited trial available	Limited trial available
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently asked questions about Business Portability Forms

Answers to common questions about validity, notarization, signatory authority, and digital signing best practices for portability requests.

Need help? Contact support

Are electronic signatures valid?
Yes. Electronic signatures are generally legally valid under the ESIGN Act (15 U.S.C. ch. 96, 2000) and state UETA laws when intent, consent, attribution, and record retention are satisfied.
When is notarization required?
Not all portability requests need notarization; certain transfers or state-specific filings may require a notary or witnesses. Verify with the receiving provider or state law before submitting.
Who can sign for the business?
An officer listed in corporate records, an authorized manager, or someone with a power of attorney may sign. Attach board resolutions or POAs when authority is not evident.
How do I correct a submitted form?
Contact the receiving provider immediately, submit an amended form with clear reference to the original, and retain both versions for audit and dispute resolution.
What evidence should accompany the form?
Provide a recent account statement, proof of business registration, government ID for the signer, and any provider-specific references requested during validation.
Electronic vs. digital signatures?
Electronic signatures are a broad legal category; digital signatures use cryptographic PKI technology. Both can be valid, but higher-risk transfers may require stronger signer authentication.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now